[Boost-bugs] [ boost-Bugs-1169920 ] Generate patches for Graph bugs in 1.32.0
Bugs item #1169920, was opened at 2005-03-24 09:49 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1169920&group_id=7586 Category: graph Group: None Status: Open Resolution: None Priority: 5 Submitted By: Douglas Gregor (dgregor) Assigned to: Douglas Gregor (dgregor) Summary: Generate patches for Graph bugs in 1.32.0 Initial Comment: There are several critical bugs in the BGL in Boost 1.32.0 that have been fixed since the release, but 1.33.0 is too far off for users to wait. We should create a patch of some sort that allows users to get at these bug fixes, without introducing any big changes into the library. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1169920&group_id=7586 ------------------------------------------------------- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs
Boost.Filesystem often has a similar problem - small fixes that could be made available sooner than waiting for the next release. Maybe some kind of public patch file or files for those who would like to apply them? --Beman
Maybe as releases are made they should be pushed off into a branch then any bug fixes applied to both the main line and the release branch. It would increases the testing load some but as the branch should not be modified very often maybe it would be possible to flag a change has been made and only run regressions if so. This way users can safely get all bug fixes applied to a release without fear that a major breaking change has been made. just an idea. Martin
On Mar 25, 2005, at 8:33 PM, Martin Slater wrote:
We already have release branches so, for instance, we could branch a 1.32.1 off 1.32.0 to provide bug fixes. However, as you mention, we'd need support for the regression testing system and at this point we don't have it. We'll get there, I hope. Doug
On Mar 25, 2005, at 10:52 AM, Beman Dawes wrote:
Or a 1.32.1... we haven't really done patch-level releases much, but with so many months in between full Boost releases it might be a good idea. I know that the libraries I work on go through a lot of changes from release to release, but some users would benefit from getting the bug fixes and nothing else. If we could make releases less painful, we'd have a shot at making this work. For now, I think I'll be providing some patches to the 1.32.0 BGL. Doug
We should make releases in smaller increments. For example, we could have made an improved release in the middle of february. Since then however, ambitious code changes have been checked in and now it will be a while. Of course the process will be that much more painful for being a much bigger bite. Robert Ramey Doug Gregor wrote:
"Robert Ramey" <ramey@rrsd.com> writes:
We should make releases in smaller increments. For example, we could have made an improved release in the middle of february.
Agreed in principle. In practice, nobody was ready to manage it. We don't have the infrastructure in place to make this work yet. -- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (6)
-
Beman Dawes -
David Abrahams -
Doug Gregor -
Martin Slater -
Robert Ramey -
SourceForge.net