I don't think we will be ready to cut a branch for the SCA 1.0 release
at the end of next week. However, there's quite a bit of new function
that has been added to trunk since we cut the branch for 0.91, so I
think having a release quite soon to deliver these improvements is
a good idea. I suggest we make the upcoming release a 1.0 beta, with
the final 1.0 release following on as the next release after that.
Simon
Raymond Feng wrote:
Comments inline.
----- Original Message ----- From: "ant elder" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, August 08, 2007 11:12 AM
Subject: Re: Release management for next release, was: SCA 0.92 release?
On 8/7/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
ant elder wrote:
> On 6/30/07, ant elder <[EMAIL PROTECTED]> wrote:
>
>> With the SCA 0.91 release now being voted on how about starting on
>> 0.92
?
>>
>> I've already been adding some things I'm interested in getting
done to
the
>> next release wiki page -
>>
http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Next+Release+Contents-so
far thats mainly related to improving web services functionality.
>>
>> So anyone else interested in helping with an 0.92 release or have any
>> function they'd like to suggest or add to the wiki page? How does
aiming for
>> getting it done 4 - 6 weeks again sound?
>>
>> ...ant
>>
>>
>>
> Bringing this thread up again as time is ticking on if we want to
get a
> release out this month. How would people feel about taking a branch
for
this
> release in a bit less than 2 weeks, say aiming for the 14/15th of
August?
> That should just about give enough time for clean up and voting to
get > a
> release out by the end of August.
>
Ant,
Thanks for reminding us that time is ticking if we want to get another
release out this month :) I'd like to nominate you as release manager,
if you're ok with it.
Thoughts?
--
Jean-Sebastien
Yes I'm ok with it, thanks for all the support. So any advance on the
name
being 0.95 and the branch being cut end of next week?
Thank you for take the responsibility. I believe we are all behind you
if you need any help :-).
For the release name, I think it should be a 1.0 as discussed on the
thread that Sebastien started.
Cutting a branch by the end of next week may be too short to contain all
the features we desire to have in the 1.0 release. I suggest two options
to be explored:
1) Try the maven-release-plugin in sandbox to better understand how it
can help reduce the overhead of releasing.
2) We could branch for the 1.0 release to contain the candidate modules
and keep doing 1.0 developement in the branch and merge them into the
trunk. I'm not sure how feasible it is.
Thanks,
Raymond
...ant
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
