[seam-dev] Release process

[Shane Bryzak]

That's a great idea, I think this is the way to go for Seam.

On 23/03/11 01:34, Pete Muir wrote:
> Why don't you use a staging repo in Nexus? We've done this with Weld for a while and it works well...
>
> On 22 Mar 2011, at 13:15, Shane Bryzak wrote:
>
>> The challenge we have is to find a release process that is compatible
>> with the Maven release plugin.  I understand the concerns about having a
>> buggy final release, and I agree with them.  I also like the idea of
>> (b), however for this *particular* release we can't continue releasing
>> CR's ad infinitum as we've already promised a (way overdue) release date.
>>
>> For future releases we can most likely go with option (b), however for
>> the time being (i.e. for the 3.0 final release) we're just going to have
>> to do our best to fix all of the issues that we discover in CR3 before
>> we go final.  At this point in time, I'm assuming that we're going to
>> have to do a 3.0.1 release within a few weeks of 3.0.0 anyway, as Seam 3
>> is essentially a new, unproven project.  For that release, let's see if
>> we can make option (b) work for us.
>>
>> Shane
>>
>> On 22/03/11 22:44, Ondřej Skutka wrote:
>>> Hi Shane / others!
>>>
>>> As the Seam 3 Final release is closing in, I'm starting to be a bit
>>> concerned about the release process. Currently, CRs are first tagged,
>>> released and afterwards go through the testing process. This is not
>>> ideal since we can end up having the final release buggy. I can see
>>> two possibilities to overcome this.
>>>
>>> a) first tag the release, then test it and then release it
>>>
>>> b) do CRs until we are satisfied with it and then switch the latest CR
>>> to Final *without* any commits
>>>
>>> I'm in favor of (b), having the advantage of community testing. WDYT?
>>>
>>> Ondra
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev