headers
Beman Dawes | 21 May 22:16
Picon
Favicon

Release schedule?

At the BoostCon '08 "Future of Boost" session there was discussion of 
release schedules, and we took a straw poll. Thanks to Hartmut Kaiser 
for recording the outcome:

○ How often do we want to have Boost releases?
§ 4 weeks: 0
§ 6 weeks: 0
§ 8 weeks: 10 votes
§ 12 weeks: 25 votes
§ 16 weeks or longer: 6 votes

Since 12 weeks was already the target we had discussed on the list, that 
seems pretty well decided as our target.

Dave Abrahams suggested that specific target dates be assigned; that 
makes the targets more specific and easier to plan around. I suggest the 
last day of the first month of each quarter:

    * January 31
    * April 30
    * July 31
    * October 31

The last day is chosen rather than the first day, because January 1st 
comes after a holiday period in which it is hard to get anything done.

So working backwards from the target date, T, what are the key 
milestones, and the time to perform the tasks involved?

* Ship release / update web sites
(Continue reading)

Permalink | Reply |
headers
vicente.botet | 21 May 22:32
Picon

Re: Release schedule?


---------------------------
Vicente Juan Botet Escriba
----- Original Message ----- 
From: "Beman Dawes" <bdawes <at> acm.org>
To: "Boost Developers Mailing List" <boost <at> lists.boost.org>
Sent: Wednesday, May 21, 2008 10:18 PM
Subject: [boost] Release schedule?

> At the BoostCon '08 "Future of Boost" session there was discussion of
> release schedules, and we took a straw poll. Thanks to Hartmut Kaiser
> for recording the outcome:
>
> ○ How often do we want to have Boost releases?
> § 4 weeks: 0
> § 6 weeks: 0
> § 8 weeks: 10 votes
> § 12 weeks: 25 votes
> § 16 weeks or longer: 6 votes
>
> Since 12 weeks was already the target we had discussed on the list, that
> seems pretty well decided as our target.
>
> Dave Abrahams suggested that specific target dates be assigned; that
> makes the targets more specific and easier to plan around. I suggest the
> last day of the first month of each quarter:
>
>    * January 31
>    * April 30
>    * July 31
(Continue reading)

Permalink | Reply |
headers
vicente.botet | 21 May 23:04
Picon

Re: Release schedule?

----- Original Message ----- 
From: "Beman Dawes" <bdawes <at> acm.org>
To: "Boost Developers Mailing List" <boost <at> lists.boost.org>
Sent: Wednesday, May 21, 2008 10:18 PM
Subject: [boost] Release schedule?

> At the BoostCon '08 "Future of Boost" session there was discussion of
> release schedules, and we took a straw poll. Thanks to Hartmut Kaiser
> for recording the outcome:
>
> ○ How often do we want to have Boost releases?
> § 4 weeks: 0
> § 6 weeks: 0
> § 8 weeks: 10 votes
> § 12 weeks: 25 votes
> § 16 weeks or longer: 6 votes
>
> Since 12 weeks was already the target we had discussed on the list, that
> seems pretty well decided as our target.
>
> Dave Abrahams suggested that specific target dates be assigned; that
> makes the targets more specific and easier to plan around. I suggest the
> last day of the first month of each quarter:
>
>    * January 31
>    * April 30
>    * July 31
>    * October 31
>
> The last day is chosen rather than the first day, because January 1st
(Continue reading)

Permalink | Reply |
headers
Beman Dawes | 22 May 16:05
Picon
Favicon

Re: Release schedule?

vicente.botet wrote:
> ----- Original Message ----- 
> From: "Beman Dawes" <bdawes <at> acm.org>
> To: "Boost Developers Mailing List" <boost <at> lists.boost.org>
> Sent: Wednesday, May 21, 2008 10:18 PM
> Subject: [boost] Release schedule?
> 
>> ...

> 
> If I have undesrood, next release *could* be on  31 july.
> Which will its containt?
> * The new libraries that have been make an explicit their intention and are 
> ready to be on the release 6 weeks before, i.e. 19 juin;

Yes, new libraries would have to be merged into branches/release by June 19.

>     Why not start already a request for new libraries inclusion, we have 
> just a month?

Yes, but I wanted to get feedback first.

>     What does it means "have been make explicit their intention and are 
> ready to", could be subjet to interpretation of the release manager, but an 
> explicit request will be welcom.
> * the upgrades done 3 weeks before, i.e. the 10 july.
> * the critical fixes up to the 31 july (Of course the release manager will 
> be impled on which fgixes are critical and which one can be done for the 
> next release.
(Continue reading)

Permalink | Reply |
headers
Daniel James | 22 May 16:39
Picon
Favicon

Re: Release schedule?

2008/5/21 Beman Dawes <bdawes <at> acm.org>:
>
> * Ship release / update web sites
> * Release candidate(s) - 7 days
> * Beta release(s) - 14 days
> * Freeze release except for showstoppers - 7 days
> * Freeze release except for bug fixes - 14 days
> * Release open for bug fixes, major library upgrades,
> and new libraries - As soon as prior release is done.

At the moment release is the basis for a possible 1.35.1 which
suggests that it isn't open for major changes yet. Will point releases
be based on another branch?

Daniel
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Permalink | Reply |
headers
Beman Dawes | 23 May 15:38
Picon
Favicon

Re: Release schedule?

Daniel James wrote:
> 2008/5/21 Beman Dawes <bdawes <at> acm.org>:
>> * Ship release / update web sites
>> * Release candidate(s) - 7 days
>> * Beta release(s) - 14 days
>> * Freeze release except for showstoppers - 7 days
>> * Freeze release except for bug fixes - 14 days
>> * Release open for bug fixes, major library upgrades,
>> and new libraries - As soon as prior release is done.
> 
> At the moment release is the basis for a possible 1.35.1 which
> suggests that it isn't open for major changes yet. Will point releases
> be based on another branch?

Yes. That way work on a point release won't delay work on the next 
regular release.

--Beman

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Permalink | Reply |

Gmane