This appears to be a variant of the "Do we reuse version numbers?" discussion of recent times. That was resolved. Can we please not rehash this?
-Chris On Wed, Jun 26, 2013 at 2:52 AM, sebb <seb...@gmail.com> wrote: > The mission of the ASF is to release software as source, and to ensure > that the released source is available under the Apache Licence. > > Before a release can be approved it must be voted on by the PMC. > The review process needs to establish that the proposed source release > meets those aims. > > It's all but impossible for reviewers to examine every single file in > a source archive to determine if it meets the criteria. > And it's not unknown for spurious files to creep into a release > (perhaps from a stale workspace - are releases always built from a > fresh checkout of the tag?) > Ok, so you are not aware of the specifics of the maven release processes as implemented by the release plugin. So you're asking a generic question. Here is how the release plugin works: release:prepare is the goal that performs some tests, changes to a non snapshot version, creates the tag, bumps up the version no and commits the changes to the pom. release:perform simply checks out the newly created tag, into a new location (ie clean) and then calls "mvn deploy". So for maven, yes, it is unknown for suprious files to creep in. -Chris
