On Thu, Jul 25, 2013 at 6:34 PM, sebb <seb...@gmail.com> wrote: > On 25 July 2013 16:55, Dennis Lundberg <denn...@apache.org> wrote: >> Den 25 jul 2013 16:08 skrev "sebb" <seb...@gmail.com>: >>> >>> On 23 July 2013 20:45, Dennis Lundberg <denn...@apache.org> wrote: >>> > Hi, >>> > >>> > This will be the final release of this shared component. After this >>> > release it will retire from the Apache Maven project and move to the >>> > Apache Archiva project. See separate vote thread about that. >>> > >>> > We solved 6 issues: >>> > >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=14389 >>> > >>> > There are no issues left in JIRA (except for the one to retire, which >>> > I'll close later): >>> > >> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&component=13272&status=1 >>> > >>> > Staging repo: >>> > https://repository.apache.org/content/repositories/maven-010/ >>> > >> https://repository.apache.org/content/repositories/maven-010/org/apache/maven/shared/maven-model-converter/2.3/maven-model-converter-2.3-source-release.zip >>> > >>> > Staging site (not synced yet): >>> > http://maven.apache.org/shared-archives/maven-model-converter-2.3/ >>> > >>> > Guide to testing staged releases: >>> > http://maven.apache.org/guides/development/guide-testing-releases.html >>> >>> What are the unique SCM coordinates? >> >> The SCM URL can be found in the pom file at the staging repo. > > As already mentioned in another thread, the staging repo URL is > temporary (and in fact can be reused for something completely > different). > > Nor does it uniquely identify the code in SCM, as the revision is missing. > > So it is not suitable for documenting the SCM coordinates.
In the normal case, where a release is approved on the first round, there is only ever one tag in SVN and it will not be changed. In these cases I do not see the value of including the revision number at all. If a release fails on the first attempt, we reuse the tag. This means that the tag will exist at multiple revisions. If you are an archealogist and find out the revision number of an ancient vote, you can look at the date/time of the vote mail and compare that to the revision dates in SVN. Still I do not see the value of this. The last tag standing is the one that got approved. Is there an ASF requirement to include the SCM revision number in a release vote? I can't find one. > >> -- >> Dennis Lundberg >> >>> >>> > Vote open for 72 hours. >>> > >>> > [ ] +1 >>> > [ ] +0 >>> > [ ] -1 >>> > >>> > -- >>> > Dennis Lundberg >>> > >>> > --------------------------------------------------------------------- >>> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> > For additional commands, e-mail: dev-h...@maven.apache.org >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
