shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan D. Cabrera" <l...@toolazydogs.com>
Subject Re: Cracking off a release
Date Thu, 13 May 2010 20:01:01 GMT

On May 13, 2010, at 11:22 AM, Kalle Korhonen wrote:

> On Thu, May 13, 2010 at 10:43 AM, Craig L Russell
> <craig.russell@oracle.com> wrote:
>> Great to hear that you're ready to "crack off" a release. You need to
>> decide:
>> Is this a final release or some early access or beta thing?
>> What tools will you use to create the release artifacts?
>> Will you release binaries or just sources (most Java projects  
>> release both
>> binary and source).
>> Who is going to be the release manager?
>
> I'll take this. Assuming Les is fine it, I'll be the release manager.
> This is a 1.0.0 GA release. We are going to release with Maven using
> the staged release process so we'll have some time to test the final
> artifact before its being released publicly and while it's being vote
> upon. If we find blockers, we'll abandon the release and do a new
> point release - 1.0.1 etc. until the staged release is accepted. While
> I haven't cut any Apache releases before, I'm fairly familiar with
> Tapestry's releases which use the same process and I've done staged
> releases with Maven/Nexus before.

Another quick comment.  If you're using Nexus staging we don't need to  
increment 1.0.x.  You can just drop the staging repository and form a  
new, fixed, one.

The release vote can have RCx in the subject w/out it being in the  
actual version that gets released.


Regards,
Alan


Mime
View raw message