[1.36.0 beta] Beta release available on SourceForge
New libraries: Accumulators, Exception, Units, Unordered. Updated Libraries: Assign, Foreach, Interprocess, Intrusive, Math, Multi-index Containers, PtrContainer, Spirit, Thread, Xpressive, plus a bunch more. Many thanks to Daniel James, Rene Rivera, Marshall Clow, Eric Niebler, the testers, and all the others who helped to get this beta release together. The beta period will be approximately one week. Please post bug reports here, but also let us hear about success stories too! --Beman
Beman Dawes wrote:
The beta period will be approximately one week. Please post bug reports here, but also let us hear about success stories too!
--Beman
Great work to all those involved. Thank you! Just to be clear. Should issue be reported "here" on the ML, in trac or both? michael -- ---------------------------------- Michael Caisse Object Modeling Designs www.objectmodelingdesigns.com
Michael Caisse wrote:
Beman Dawes wrote:
The beta period will be approximately one week. Please post bug reports here, but also let us hear about success stories too! --Beman
Great work to all those involved. Thank you!
Just to be clear. Should issue be reported "here" on the ML, in trac or both?
Please report all issues to the mailing list, but if an issue is complex, accompanied by a patch file, or something likely to be deferred until the next release then also add a trac issue. Thanks, --Beman
on Thu Jul 31 2008, Beman Dawes <bdawes-AT-acm.org> wrote:
Michael Caisse wrote:
Beman Dawes wrote:
The beta period will be approximately one week. Please post bug reports here, but also let us hear about success stories too! --Beman
Great work to all those involved. Thank you!
Just to be clear. Should issue be reported "here" on the ML, in trac or both?
Please report all issues to the mailing list, but if an issue is complex, accompanied by a patch file, or something likely to be deferred until the next release then also add a trac issue.
Beman, you are the release manager so I want us to do whatever you consider most workable, but I have to question the policy of ever encouraging people to report issues to this list. In general the tracker sends email to the people concerned anyway, and if we haven't already done so we can arrange for it to send issue updates to a mailing list to which you (or even this list) can be subscribed during a release run-up. It's just that I think having a record of everything is important to making sure things don't slip through the cracks (e.g. "apply this quick fix to the trunk or development branches so it isn't lost" can be handled by reassigning the ticket), and these records are often useful in the future. -- Dave Abrahams BoostPro Computing http://www.boostpro.com
participants (3)
-
Beman Dawes -
David Abrahams -
Michael Caisse