[1.49.0] New libraries?
What new libraries are ready for 1.49.0? What is that state of any new libraries that want to go in 1.49.0? Are they in trunk and do the developers think they are ready to be merged into release? The release managers would like to have a four week beta period of 1.49.0. That means we have to get going on new libraries right way if we are going meet our early February release schedule. --The release team
On 11/30/2011 11:29 AM, Beman Dawes wrote:
I would like to get the TTI library in Boost 1.49 but I am working regularly on a job now and still have much to do on TTI. Nevertheless I anticipate some free time over the Christmas holidays/New Years day period when I will have time off to possibly finish up. Can you give an idea of the cutoff date when a library needs to be in acceptable form on the trunk in order to make it into Boost 1.49 ?
On 11/30/2011 5:20 PM, Edward Diener wrote:
We're asking so that we can form an idea of when we should set the cutoff. But I can tell you that late December will undoubtedly be too late. :-( -- Eric Niebler BoostPro Computing http://www.boostpro.com
On Nov 30, 2011, at 8:10 PM, Eric Niebler wrote:
I'm waiting for a review result, and will probably need some time to comply with the review manager's changes. I would really like to get the Algorithms library into 1.49 (assuming it is approved, that is). -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki
On 11/30/2011 8:17 PM, Marshall Clow wrote:
Marshall, best at this point to aim for 1.50. -- Eric Niebler BoostPro Computing http://www.boostpro.com
On 11/30/2011 11:10 PM, Eric Niebler wrote:
OK, then I will try to get TTI will into 1.50. I just do not have the time to finish it before the holidays for 1.49. But I do think that Boost needs to specify, for each release date, the cutoff date for libraries to make it into that release. If that can not be done then it is difficult for the developer of a new library to know if he can finish work in time for a given release. Is it not possible to publish somewhere, a priori, when each release is expected to come out as well as the cutoff date for new libraries to be ready for that release ?
On 12/1/2011 2:55 PM, Edward Diener wrote:
It is usually published on the Boost calendar (see http://www.boost.org/development/index.html). There had been some recent discussion on the list about extending the beta period for releases, so the 1.49 schedule is still flux while we try to accommodate that feedback. Once we know for certain, it'll go on the calendar and there will be an announcement here. Thanks, -- Eric Niebler BoostPro Computing http://www.boostpro.com
On 12/2/2011 1:19 AM, Eric Niebler wrote:
That is really a poor way for anybody to determine when Boost release dates and cutoff dates occur. Even moving through the calendar by month tells me nothing about this.
How about some page where the release dates and cutoff dates are mentioned for the next for the next release at the very least ?
Thanks,
On 12/2/2011 5:10 AM, Edward Diener wrote:
If you switch the calendar to the agenda tab you get that list of dates. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
On 12/2/2011 5:18 PM, Edward Diener wrote:
As we've been saying, the 1.49 schedule is in flux, bear with us. -- Eric Niebler BoostPro Computing http://www.boostpro.com
i have two libraries, which i'd like to merge into trunk (hopefully before 1.49). boost.heap it is in good shape, i still need to check one issue before merging it into trunk. i've also submitted one patch for boost.parameter [1], that should be applied so that boost.heap cleanly compiles. boost.lockfree it depends on boost.atomic, which itself has been accepted, but i am not sure, if it is ready to be merged into trunk. however i could provide an older version of boost.atomic as implementation detail, if boost.atomic won't be ready for 1.49. cheers, tim [1] https://svn.boost.org/trac/boost/ticket/6177
On 12/1/2011 12:21 PM, Tim Blechmann wrote:
You're free at any time to make changes to trunk. Fire away. We're only concerned with merging new libraries to the release branch. -- Eric Niebler BoostPro Computing http://www.boostpro.com
participants (6)
-
Beman Dawes -
Edward Diener -
Eric Niebler -
Marshall Clow -
Rene Rivera -
Tim Blechmann