I ask this not to badger well-intentioned volunteers, but to provoke constructive discussion. Version 1.34.1 was released on July 24, 2007, going on 8 months ago. Since that time 6 new libraries have been accepted with one more accepted provisionally (according to boost.org website). Prior to 1.34.1, 1.34.0 was released on May 12, 2007, 2-1/2 months prior. 1.34.0 was considered a very long release: it's predecessor (1.33.1) was released on Dec. 5, 2005, nearly 1-1/2 years prior. At one point, there was hope of getting 1.35.0 out before the end of 2007, given that it was to be a short release primarily to move to Trac and Subversion, without large functionality upgrades or code base improvements. As I recall, part of the intent was to move to faster release cycles with teams of release managers to reduce the imposition on any one volunteer. We are now nearing spring break, the beaches of Cancun beckon, and another round of messages about Google's Summer of Code have begun. Is there a realistic target date for releasing 1.35? Is there a distinct possibility that 1.35 will require a full year or more to close since it began? With respect, Richard Newman
Richard Newman wrote:
I ask this not to badger well-intentioned volunteers, but to provoke constructive discussion.
Version 1.34.1 was released on July 24, 2007, going on 8 months ago. Since that time 6 new libraries have been accepted with one more accepted provisionally (according to boost.org website).
Prior to 1.34.1, 1.34.0 was released on May 12, 2007, 2-1/2 months prior. 1.34.0 was considered a very long release: it's predecessor (1.33.1) was released on Dec. 5, 2005, nearly 1-1/2 years prior.
At one point, there was hope of getting 1.35.0 out before the end of 2007, given that it was to be a short release primarily to move to Trac and Subversion, without large functionality upgrades or code base improvements. As I recall, part of the intent was to move to faster release cycles with teams of release managers to reduce the imposition on any one volunteer.
We are now nearing spring break, the beaches of Cancun beckon, and another round of messages about Google's Summer of Code have begun.
Is there a realistic target date for releasing 1.35? Is there a distinct possibility that 1.35 will require a full year or more to close since it began?
RC1 will be generated in the next couple of days. The reaction to that will be critical in determining when 1.35.0 ships. --Beman
John Maddock wrote:
Beman Dawes wrote:
RC1 will be generated in the next couple of days. The reaction to that will be critical in determining when 1.35.0 ships.
Beman, do you have a TODO list somewhere? I should be able to help out a bit over the next few weeks.
Take a look at http://svn.boost.org/trac/boost/wiki/MergeOneDotThreeFiveDotZero. A specific task you could take on is beating the release history into shape. It is embarrassing to have this release with many new libraries, yet most are missing from the release history! Another thing that would help is to think about release candidate QA. I'll start a separate thread about that. --Beman
Beman Dawes wrote:
John Maddock wrote:
Beman Dawes wrote:
RC1 will be generated in the next couple of days. The reaction to that will be critical in determining when 1.35.0 ships.
Beman, do you have a TODO list somewhere? I should be able to help out a bit over the next few weeks.
Take a look at http://svn.boost.org/trac/boost/wiki/MergeOneDotThreeFiveDotZero. A specific task you could take on is beating the release history into shape. It is embarrassing to have this release with many new libraries, yet most are missing from the release history!
Yep, and I added one of them :-( OK: I've found the release history in the Website directory, and I can regenerate the RSS from the quickbook source, but how do I go about testing the resulting RSS? Rene? John.
participants (3)
-
Beman Dawes -
John Maddock -
Richard Newman