Chuck Murcko wrote:
> 1) tag releases of httpd subprojects intended for release with the
> tagname
> that httpd uses for the same release (simplifies CVS assembly of src)
>
> 2) packaged release drops go into a subdir named by the httpd release
> they go
> with; i.e., httpd, so httpd-proxy/stable/apache-1.3.20 or
> httpd-proxy/stable/httpd-2.0.
The trouble is that this means the subproject people are going to have
coordinate with the RM to create the directory with the release number
in it all the time, which will be a pain.
How about a /httpd-proxy/stable/ directory containing the latest fixed
code in it? The development could then happen in a /httpd-proxy/devel/
directory, and when the new development code is stable, the changes get
committed to the /stable/ tree...?
Patches would then go in a /httpd-proxy/patches/apache-1.3.20/
directory.
The RM will then pull in the code from the /stable/ directory at roll
time - the module people (us) won't need to do anything except make sure
whatever is in /stable/, is stable.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
