On Wednesday, May 2, 2001, at 06:05 PM, Graham Leggett wrote:
> Chuck Murcko wrote:
>
>> OK, but we still need to maintain the old releases somehow other than
>> as
>> CVS tags, no? I.e.; where does the packaged 1.3.19 proxy distribution
>> go
>> when we move on to 1.3.20?
>
> Not necessarily - if you're looking for the version shipped with
> apache-1.3.19, just look in the apache-1.3.19.tar.gz archive.
>
If that's how the distribution ships, that's fine with me.
>> The stable subdirectory is actually supposed to be the same release
>> number the httpd distrib is cut with, to allow scripting the work. So
>> the directories only get created with a new release. When 2.0.18 proxy
>> releases, you make the 2.0.19 dirs and drop code there. Some other
>> naming rule might work better.
>>
>> The subproject people could get a serial "token" from the release
>> manager and pass this among themselves while they integrate, and last
>> subproject guy hands it back to the RM saying "this is a rollup release
>> candidate".
>>
>> We can specify a time (24-48 hours? Less?) to complete each subproject
>> integration to keep the process moving along.
>
> The trouble is that doing this will probably take too long - it means
> that too many people are trying to coordinate things, which leaves too
> much room for things to go wrong.
>
>
Well, not if you say "OK, we roll on xx/yy at zzzz GMT, so all you
subproject geeks be ready!" People with subprojects can announce they
are ready to integrate any time in between the announcement and the
rollup build, give or take.
Then the RM rolls at the appointed time. This also rolls in the
subprojects.
Chuck Murcko
Topsail Group
http://www.topsail.org/
