Jason van Zyl wrote:
On 20 Sep 06, at 3:04 PM 20 Sep 06, Steve Loughran wrote:
Daniel Jemiolo wrote:
> The Muse development team has worked hard over the spring and summer
> months, enhancing, refactoring, fixing, and polishing the 2.x code
base,
> and the time has come to vote on a release for version 2.0.0. I am very
> proud of the members of our team - both the committers who have
> contributed and taken responsibility for large sections of code, and
> non-committers who have rolled up their sleeves and wrestled with the
> code, samples, and build artifacts until the project met the
expectations
> we had set for it. I'm also excited to see other open source projects
> already using our code, as it gives us fresh perspectives on how to
make
> WSRF and WSDM easier for other programmers.
>
> To the committers and PMC members: please cast your vote on the
release of
> Muse 2.0.0, the artifacts for which are found here:
>
> http://www.apache.org/~danj/muse/2.0.0
>
> Here's my +1 for this release.
>
Daniel,
I'm going to vote -1 until the binaries dont include any dependent
jars marked -SNAPSHOT
This problem can easily be alleviated using the release plugin. I also
had an experience the other day that leads me to believe that official
releases should be barred unless you use the release plugin. Exposing
the options to enable release info should be turned off. Usually it's
inadvertent but it happens all the time. I was helping Dan (Xfire) the
other day and he did a release by enabling the updateReleaseInfo
property so he release the JARs only. The sources and javadoc did not go
up which is bad. There should only be one way to do a release and the
release should go through archiva which could detect the intactness of a
release. Releases without sources or Javadocs should just get rejected,
and if the release plugin is used it's impossible for SNAPSHOTs to slip
through. As far as releases go, if projects don't use the release plugin
it's not a release.
+1 to that.
Perhaps the Apache repository could somehow detect which artifacts had
been tagged as formally released, or at least approved by archiva. Of
course, non-maven projects still have the right to update content, but
their stuff may need to go through some staging process before it is
accepted as legitimate.
-Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
