Mailing-List: contact dev-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: domain of gozer@ectoplasm.org
 designates 66.34.202.202 as permitted sender)
Message-ID: <41BAA0E8.9000409@ectoplasm.org>
Date: Fri, 10 Dec 2004 23:25:28 -0800
From: "Philippe M. Chiasson" <gozer@ectoplasm.org>
User-Agent: Mozilla Thunderbird 0.9 (Macintosh/20041103)
MIME-Version: 1.0
To: Stas Bekman <stas@stason.org>
Cc: mod_perl Dev <dev@perl.apache.org>
Subject: Re: mp2: RC1..N..2.0 plan
References: <41BA7AB4.7040107@stason.org>
In-Reply-To: <41BA7AB4.7040107@stason.org>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig1D5BDB2348495C992048949E"

--------------enig1D5BDB2348495C992048949E
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Stas Bekman wrote:

> So if the nightly smoke goes well, tomorrow gozer releases RC1. We 
> aren't going do the usual drill of release candidates, we are just 
> going to release RCs. So the plan is:
>
> we release RC1
> - people report problems - we fix them
> - we still work on knowns issues to be resolved before 2.0
> we release RC2
> - people report problems
> - we still work on knowns issues to be resolved before 2.0
> we release RC3
> ...
> we release RCN
> - people report no problems

 - people report no problems we consider 2.0 blockers

> - we have no more planned fixes for 2.0
> we release 2.0

Sounds good to me.

>
> Now versioning. First of all mp2 is going to be 2.0.x, since it looks 
> like Apache 2.2 might be different enough that modperl-2.2.x will appear.

> We can't give interim RCs $VERSION = 2.0.0 since once we release 2.0 
> we can't change any API, with RCs we hope we won't but if something is 
> really bad we will. Moreover we must keep raising the version numbers 
> so we can continue tracing the bugs. If RC1 is called 2.0.0 and the 
> final release is called 2.0.0 this is going to be a big mess. So the 
> solution is:
>
> continue RCs versions as 1.99_18, 19, 20, etc. But change Makefile.PL 
> to have:
>
>   VERSION modperl-2.0.0-RC1
>
> so it's clear from the package that's an RC for 2.0.0.

Yes, I think it's a good way to go about it. There remains the slight 
probability of trouble for 3rd party authors that have
bugs in their MP 2.0 detection code, but that's not a very big problem.

> Now wish us good luck and hopefully RC1 will be out tomorrow.

--------------------------------------------------------------------------------
Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5 
http://gozer.ectoplasm.org/     F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5


--------------enig1D5BDB2348495C992048949E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBuqDvyzKhB4jDpaURAikqAJ4l8YgHz/oNc+ck38qQnz3lrGHqpACeML7g
yG1uzLlRDyQnSiWhL/FmREc=
=Q7N7
-----END PGP SIGNATURE-----

--------------enig1D5BDB2348495C992048949E--