httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <>
Subject Re: Proposed ANNOUNCE for 1.2.2 (II)
Date Mon, 11 Aug 1997 15:29:52 GMT
Traditionally, test tarballs have been test tarballes; not release ready
and a new one has to be rolled.  Once the new one deemed to be the final
version is rolled, then it is left for a day or two and people test it
even more before being released.  By the time we got to rolling the final
tarball, it was almost certain that either that version would go out and
the version was incrementend to the next -dev right away.

You are doing things differently.  It did not appear clearly to me that
you were doing things that way.  That is the biggest cause of my concern.

I prefer doing it the old way, but that is just my preference.  If people
like this way, thats fine.  Just make it clear...

On Mon, 11 Aug 1997, Ralf S. Engelschall wrote:

> Hmmmm... then please show me how I have to roll the tarball which should act
> first as a pre-release and (if successfully tested) as the final tarball?  I
> have to change the version to 1.2.2 and tag the source. The idea was to retag
> only when new patches occur or the tarball failed. Ok, the 2nd pre-release
> tarball is still successfull, but because of your patch I adjusted the
> APACHE_1_2_2 tag and do a 3nd tarball for the final release. No problem.  And
> I couln't said this before because before I didn't know that we need a 3nd
> tarball....
> Marc, I really don't know a way to produce a proposed tarball without changing
> version to 1.2.2 and tagging the sources when we really want to use this
> tarball for final release. Or did I miss something?
>                                        Ralf S. Engelschall

View raw message