On Tue, May 4, 2010 at 1:41 PM, Antonio Petrelli <[email protected]> wrote: > In what sense? The pom (without modules) is not released as an > archive, but only inside Maven repository, and it has only the pom.xml > itself (along with metadata and signatures), nothing more.
It's a released artifact because it's housed in a publicly accessible place where only vetted artifacts go. To be clear (and especially for Mick's sake) the svn repo is not considered a release even though it's publicly available. The svn repo is public for the sake of openness and shared development. But a release is something different. It's an artifact that has been vetted by an entity of the foundation to be safe for public consumption under the Apache license. Once we move something from svn to a public place and say "this is a release" we're saying "I've looked at this artifact and verify that it is correct." We can't officially say that until an artifact has been produced and staged. Once a staged artifact is approved by the PMC we move that staged artifact into a public place and call it a release. That process ensures that the artifacts that are released are the artifacts that were voted on. > I must confess that, in this case, I don't know the process very well. Same here. I've been a bit unclear on that process as well, but I do know that anything we call "released" has to be staged and approved. > However I would like to have the least bureaucracy possible, for the release > of a mere pom Agreed. Unfortunately, it seems like this process is necessary - though I don't think it's all too difficult is it? Greg
