On Wednesday, September 19, 2001, at 05:53 PM, Chuck Murcko wrote:
> I think we need to think about these kinds of issues before we pick
> names for apr tags and release bundles.
>
I also think that we should call what we release httpd-2.0 (or
apache-2.0, whatever), and that one source release should contain all
the httpd source code we supply. Binary builds can always used an
agreed-upon configure list of options. I think we should rename the
current httpd-2.0 repository to httpd-core-2.0 or something similar, and
make the server core, along with apr, apr-util, and all the modules,
separate CVS modules in httpd-2.0 (the one and only place from which we
do an httpd project release at version 2.0). If a module or other
subproject doesn't change between release versions, you just tag it when
you make the next release tag for the release repository. So httpd-
proxy/module-2.0 is always used to build httpd-2.0, since it's a CVS
module. So is httpd-proxy/module-2.1, which gets used to build httpd-2.1
source repository. We don't need to maintain separate source trees, just
assemble the server from the CVS modules as a repository.
If the httpd-2.0 repository were organized as CVS modules, this would be
easy to do. So we're talking possibly fundamental changes to how we
develop and release here.
Regards,
Chuck
