Yeah, normally a tarball is done right after the tagging... so the tarball tested is the the one that is actually distributed, assuming all works out OK.
Bill Stoddard wrote: > > Good message from Mark that is worthy of discussion... > > > ----- Original Message ----- > From: "Mark J Cox" <[EMAIL PROTECTED]> > To: "Bill Stoddard" <[EMAIL PROTECTED]> > Sent: Thursday, October 04, 2001 11:03 AM > Subject: Re: Tagging 1.3.21 now > > > > Bill; normally the RM releases a tarball at this stage, so we can test the > > whole package (which might be missing files etc). Otherwise anyone > > wanting to test has to pull the tree with the right tag and go through the > > release process to get a kosher tarball. (there is supposed to be 24 > > hours between the release of the tarball on dev.apache.org for testing, > > and the real public release) > > > > Cheers, > > Mark > > > > Yes I understand. I am adopting a process tweak that seems to work well for Apache >2.0. > People can extract APACHE_1_3_21 to test the obvious things like "will the server > compile". If we have minor breakage that can easily be fixed, we make the changes >and > bump the tag. I put an arbitrary time limit of 24 hours on this phase of the T&R >process. > > At the end of 24 hours, we either abandon the tag (because there were just too many > problems) or roll the tarball and start the tarball test cycle. > > I believe this process results in a slightly reduced workload for the RM (in the >cases > where the TAG had to be abandonded). Also, missed version numbers look bad to the >user > community and invariably generates questions like (was 1.3.blah ever released? why >not? > yadda yadda yadda). > > Bill > -- =========================================================================== Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither"
