Re: [boost] 1.30.0 branch-for-release complete
At 09:58 AM 3/4/2003, Peter Dimov wrote: >Beman Dawes wrote: >> At 04:01 PM 3/3/2003, Mark Rodgers wrote: >> >> >Is it time we introduced beta releases into the release procedure? >> It >seems to me that it would be a good idea to tar up 1.30.0 RC and >> give >everyone a chance to try it out and report feedback without >> having to >use CVS. I know CVS puts me off. >> > >> >Questions include >> > >> >How much of a hassle would it be for someone? (Beman?) >> >> Not much. But I'd like to get an indication people will really try a >> beta before we go to the trouble. > >If we don't make a beta (RC) available, it'd be difficult to get an >indication about people's willingness to try one. Good point. >FWIW, I think that people will try the beta releases. Saves much trouble in >the long run. OK, let's work out the details. My first thought is not to run the beta through the SourceForge release process, but just to post it boost.sourceforge.net like we do with the regression tests. --Beman ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] 1.30.0 branch-for-release complete
Beman Dawes wrote: > At 04:01 PM 3/3/2003, Mark Rodgers wrote: > > >Is it time we introduced beta releases into the release procedure? > It >seems to me that it would be a good idea to tar up 1.30.0 RC and > give >everyone a chance to try it out and report feedback without > having to >use CVS. I know CVS puts me off. > > > >Questions include > > > >How much of a hassle would it be for someone? (Beman?) > > Not much. But I'd like to get an indication people will really try a > beta before we go to the trouble. If we don't make a beta (RC) available, it'd be difficult to get an indication about people's willingness to try one. FWIW, I think that people will try the beta releases. Saves much trouble in the long run. ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] 1.30.0 branch-for-release complete
At 04:01 PM 3/3/2003, Mark Rodgers wrote: >Is it time we introduced beta releases into the release procedure? It >seems to me that it would be a good idea to tar up 1.30.0 RC and give >everyone a chance to try it out and report feedback without having to >use CVS. I know CVS puts me off. > >Questions include > >How much of a hassle would it be for someone? (Beman?) Not much. But I'd like to get an indication people will really try a beta before we go to the trouble. >How many extra people would be encourage to test the beta? Good question. Are there others interested in a beta? Thanks, --Beman ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] 1.30.0 branch-for-release complete
Is it time we introduced beta releases into the release procedure? It seems to me that it would be a good idea to tar up 1.30.0 RC and give everyone a chance to try it out and report feedback without having to use CVS. I know CVS puts me off. Questions include How much of a hassle would it be for someone? (Beman?) How many extra people would be encourage to test the beta? How many beta releases should we do? Mark ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] 1.30.0 branch-for-release complete
At 06:45 PM 3/1/2003, David Abrahams wrote: >Beman Dawes <[EMAIL PROTECTED]> writes: > >> The tag is RC_1_30_0 > >Didn't we agree that we were going to tag the trunk and generally do >any merges from the trunk to the branch? This tag appears to be on >the branch AFAICT. There was a lot of discussion, but more\release_procedures.htm never got updated AFAIK. I don't mind using a new procedure, but it needs to be documented. Someone (Jeff Garland?) circulated a draft, but I don't think it was ever finalized. See http://aspn.activestate.com/ASPN/Mail/Message/1411802/release_procedures.htm --Beman ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Re: [boost] 1.30.0 branch-for-release complete
Beman Dawes <[EMAIL PROTECTED]> writes: > The tag is RC_1_30_0 Didn't we agree that we were going to tag the trunk and generally do any merges from the trunk to the branch? This tag appears to be on the branch AFAICT. -- Dave Abrahams Boost Consulting www.boost-consulting.com ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
[boost] 1.30.0 branch-for-release complete
The tag is RC_1_30_0 I'm going to take a break for the rest of the weekend, and then we should get together a list of what needs to be done before the actual release. Thanks, --Beman ___ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
