Mailing-List: contact shiro-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: shiro-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-Id: <5BA0F44F-E1BD-4FFD-B5A8-FD38E760880C@oracle.com>
From: Craig L Russell <craig.russell@oracle.com>
To: shiro-dev@incubator.apache.org
In-Reply-To: <AANLkTikj--M_55nk9KpqSycuMH190PnUP8EM1Fp6CEDt@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Subject: Re: Cracking off a release
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 14 May 2010 10:40:48 -0700
References: <9F623656-D8DA-436D-96D1-975193172D58@toolazydogs.com>
 <AANLkTinMoYSbJ961zwlEz5bJ7xhOJzHt4MUA9SBLvJtp@mail.gmail.com>
 <125B0ED8-08EB-4471-A638-44D9FFBEB421@oracle.com>
 <AANLkTim0zB7Y0Kg7Fn8X-CKgZMrJbgxKPGzkwGw7YyWM@mail.gmail.com>
 <AANLkTikj--M_55nk9KpqSycuMH190PnUP8EM1Fp6CEDt@mail.gmail.com>

Hi Tauren,

For me, the reason to do a x.x.x-RC1 *release* would be to give the  
community a chance to test it out, give feedback, report bugs, etc.  
This is what a commercial entity would do as it prepared for a final  
release.

We are not in the same situation. The code is ready for release, and  
we don't plan on publishing the -RC1 release for folks to try. We're  
planning on building what will be 1.0.0. Negative feedback we get on  
the 1.0.0 will mean we got something wrong in the process (e.g.  
licenses, artifact names) and needs a respin, not that we need  
improvements in the feature set, doc, etc.

Craig

On May 13, 2010, at 11:38 AM, Tauren Mills wrote:

> I'm curious why you wouldn't do release candidates, such as 1.0.0-RC1,
> 1.0.0-RC2 and have 1.0.0 GA be the final accepted release. This  
> isn't a
> complaint, do it however you wish, I'm just interested to know the
> reasoning.
>
> Tauren
>
>
> On Thu, May 13, 2010 at 11:22 AM, Kalle Korhonen <kalle.o.korhonen@gmail.com
>> 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.
>>
>> Kalle
>>
>>
>>> After you know what to release and who is going to create the  
>>> release
>>> artifacts, you can proceed to step 2: creating the release  
>>> artifacts.
>> There
>>> are many examples of releases from incubation that you should  
>>> probably
>> study
>>> and then volunteer to cut the release(s).
>>>
>>> The first release of a podling is normally reviewed by a small  
>>> number of
>>> really dedicated volunteers who find many trivial-sounding  
>>> problems that
>> in
>>> fact are very important. But whoever volunteers to be the release  
>>> manager
>>> should expect between two and five attempts before passing muster  
>>> for an
>>> official Apache incubating release.
>>>
>>> Craig
>>>
>>> On May 13, 2010, at 9:47 AM, Les Hazlewood wrote:
>>>
>>>> We're working on it! :)
>>>>
>>>> Seriously though - I think we can be code complete today.  After  
>>>> that
>>>> is finished, I was going to ping the list to ask the Mentors how  
>>>> we go
>>>> about starting the voting process.  Since we might be able to start
>>>> this tomorrow, could you fill us in a bit on how this works?
>>>>
>>>> Thanks!
>>>>
>>>> Les
>>>>
>>>> On Thu, May 13, 2010 at 8:28 AM, Alan D. Cabrera <list@toolazydogs.com 
>>>> >
>>>> wrote:
>>>>>
>>>>> :)
>>>>>
>>>>> We've been at this for quite some time.  I've been approached by  
>>>>> people
>>>>> wondering when this is going to happen.
>>>>>
>>>>> I think that a release would be a good idea.  Thoughts?
>>>>>
>>>>>
>>>>> Regards,
>>>>> Alan
>>>>>
>>>>>
>>>
>>> Craig L Russell
>>> Architect, Oracle
>>> http://db.apache.org/jdo
>>> 408 276-5638 mailto:Craig.Russell@oracle.com
>>> P.S. A good JDO? O, Gasp!
>>>
>>>
>>

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!