httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Laurie <>
Subject Re: Apache 2000, err Apache 2.0 gets real
Date Fri, 30 Jul 1999 22:22:17 GMT
Bill Stoddard wrote:
> Steps to an Apache 2.0 beta release:
> 1. Create a clean Apache 2.0 repository
>         Move the mpm repository into a non Apache 2.0 tree. Move the
> repository, rename it, whatever. How it's done is not important. We just
> need a clean Apache-2.0 repository to begin work in.  Perhaps create a
> new apache-sandbox repository and put both apache-apr and apache-mpm
> into it.
> When: ASAP. AFAIK, Brian is the only person who has authority to do
> this. Brian?
> 2. Seed/Populate Apache 2.0 repository
>         This is the first of a multi step process to build the Apache 2.0 beta
> release candidate. The repository is initially populated with a merge of
> the Apache 1.3.7 release and the apache-apr repository.
> When: ASAP. Should take a day to complete. Manoj has volunteered.

Why not MPM as the starting point? I'm not sure which causes most pain,

> 3. Begin APR'izing the Apache 2.0 repository
> When: Ryan tells me he can get the initial work done in 2 or 3 weeks.
> Much debugging follows. End of Aug?
> 4. Convert Apache 2.0 to use autoconf
> When: ? I don't 'do' autoconf so I have no idea :-)
> 5. Hand merge select apache-mpm work into apache-2.0
>         Specifically, add the mpm module restructure and the API hook work.
> When: ?

Before 3. That much is obvious. Step 2 really should be merge APR/MPM
work and _then_ start screwing around.




"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
     - Indira Gandhi

View raw message