Hi David, On 30/04/07, David Illsley <[EMAIL PROTECTED]> wrote:
Jeremy, From watching a number of WS-Commons and Axis2 releases, it appears that neither project votes on release binaries in line with the way the Incubator does things, we seem to simply vote on the principle of having a release soon with a given feature-set. I don't believe that in and of itself that's a problem...
I guess I've got a bit more used to the Incubator-way lately :-) Certainly WS & Incubator are two different communities so if there are things from Incubator or elsewhere that the WS community feel make sense in WS then lets propose / vote on them. I think voting on the binaries is one which is used by other Apache projects as well as orgs outside Apache.
However, we've now had a couple of Axiom and Axis2 releases in the recent past where the need for an x.y.z + 0.0.1 release has become apparent within days of a release (the most recent at [1]). The impact of lack of community testing on real Release Candidates is, imo showing up in clear fashion. Given that, I'm thinking of proposing that we adopt the incubator method of publishing a real Release Candidate build + associated SVN revision number that we vote on, rather than voting on "having a release soon".
I'd like to help here.
N.B. This isn't meant as criticism of anyone, but an observation that the current method seems to be producing less that ideal results. Thoughts/Comments/Suggestions? David [1] http://issues.apache.org/jira/browse/AXIS2-2607
Cheers, Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
