Comment inline.
Simon
Jean-Sebastien Delfino wrote:
Some thoughts inline.
ant elder wrote:
We've started talking about an 0.92 release way back on June 30th
saying it
would be in August. To make this happen takes a minimum of two 3 day
votes,
past releases show we always need at least 2 release candidates, so to
ensure we get a release out in August we need the first RC by about
August
22nd, though to be certain this happens in August i'd be more comfortable
with allowing time for the possibility of a third RC which means the
weekend
of 17th/18th - ie. the end of next week.
+1 for cutting a branch on the 18th
We've said we'd have an August release so i think we should try to
make this
happen, doesn't matter so much what we call it. What do others think -
should we aim for an August release or let it slip a bit to allow more
things to get done?
...ant
+1 for aiming for an August release
On 8/8/07, Simon Nash <[EMAIL PROTECTED]> wrote:
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
+1 for 1.0-beta, I don't think we're ready for a 1.0 final but with
everything we've added and fixed recently, 1.0-beta is about right IMO.
Raymond Feng wrote:
[snip]
1) Try the maven-release-plugin in sandbox to better understand how it
can help reduce the overhead of releasing.
+1
I'm not a Maven expert but if I remember correctly it has been mentioned
several times, so I think we should try.
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.
+1
I think it's feasible if "doing 1.0 development" is about stabilizing
the 1.0 release branch, which I guess a release branch is for :) That
means:
- No completely new function, only bug fixes and improvements.
- No changes to dependencies or structure of the distro (unless required
to fix a major bug, and approved by the RM).
- Commits go with a full build of the runtime, itests, samples and
demos, and verification that the samples still work following the steps
documented in their readmes.
How soon would we be moving into this mode? I presume it would be after
we have released 1.0-beta. Does anyone think it would be sooner than that?
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
