[1.35.0] Volunteer[s] wanted: Building release snapshots
In the past, the release manager has waited until a release is almost ready, and then started building and posting release candidates. Getting set up to generate the release candidates takes longer than expected. The release candidates themselves turn out to be missing files or have other problems that take longer than expected to resolve. I propose we start building daily release snapshots, regardless of where we are in a release cycle. I'm calling these "snapshots" rather than "candidates", since they are really only release candidates late in the release cycle. Building snapshots on a daily basis would have these benefits: * The mechanical procedure would become smooth, and so could eliminate one of the delays that plague the current release process. * The snapshots could be inspected, tested, and otherwise checked for quality control on an ongoing basis. Since release tarball problems could be detected and fixed earlier in the release cycle, this could reduced or eliminated a source of delays. * The release workload could better distributed, since generation of snapshots could be handled by someone other than the release manager. Comments? Would anyone like to volunteer to take this on? They would need a high speed internet connection as the files involved are quite large. --Beman
On Feb 1, 2008, at 9:23 AM, Beman Dawes wrote:
In the past, the release manager has waited until a release is almost ready, and then started building and posting release candidates. Getting set up to generate the release candidates takes longer than expected. The release candidates themselves turn out to be missing files or have other problems that take longer than expected to resolve.
I propose we start building daily release snapshots, regardless of where we are in a release cycle. I'm calling these "snapshots" rather than "candidates", since they are really only release candidates late in the release cycle.
Building snapshots on a daily basis would have these benefits:
* The mechanical procedure would become smooth, and so could eliminate one of the delays that plague the current release process.
* The snapshots could be inspected, tested, and otherwise checked for quality control on an ongoing basis. Since release tarball problems could be detected and fixed earlier in the release cycle, this could reduced or eliminated a source of delays.
* The release workload could better distributed, since generation of snapshots could be handled by someone other than the release manager.
Comments?
Would anyone like to volunteer to take this on? They would need a high speed internet connection as the files involved are quite large.
--Beman _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/ listinfo.cgi/boost
Hello, New here and I would like to try building boost 1.35.0 on OS X since there are build problems with the 1.34.1 release. I am pulling CVS head from the sourceforge site, is that the correct location to pull from? BTW, the 1.34.1 problem was a bad rpath in the built dylibs. -- Mike Jackson Senior Research Engineer Innovative Management & Technology Services
on Fri Feb 01 2008, Mike Jackson <imikejackson-AT-gmail.com> wrote:
On Feb 1, 2008, at 9:23 AM, Beman Dawes wrote:
In the past, the release manager has waited until a release is almost ready, and then started building and posting release candidates.
Please start a new thread for new topics.
Hello, New here and I would like to try building boost 1.35.0 on OS X since there are build problems with the 1.34.1 release. I am pulling CVS head from the sourceforge site, is that the correct location to pull from?
No, you'll want to get it from http://svn.boost.org using subversion. -- Dave Abrahams Boost Consulting http://boost-consulting.com
Hi.
since there are build problems with the 1.34.1 release. I am pulling CVS head from the sourceforge site, is that the correct location to pull from?
No, you'll want to get it from http://svn.boost.org using subversion.
Should someone finally shut down the sourceforce CVS repository for Boost? Any point to it existing any more? Seems like it serves not purpose and can only saw confusion. Best regards, Jurko Gospodnetić
Jurko Gospodnetić wrote:
Hi.
since there are build problems with the 1.34.1 release. I am pulling CVS head from the sourceforge site, is that the correct location to pull from? No, you'll want to get it from http://svn.boost.org using subversion.
Should someone finally shut down the sourceforce CVS repository for Boost? Any point to it existing any more? Seems like it serves not purpose and can only saw confusion.
I was wondering about that too. And we need to update the web site to point to http://svn.boost.org. Maybe it would be easier to wait until 1.35.0 ships. --Beman
participants (4)
-
Beman Dawes -
David Abrahams -
Jurko Gospodnetić -
Mike Jackson