On Mon, 2015-11-09 at 12:30 +0100, Stefan Egli wrote:
> -0
>
> not sure if we should reuse version numbers for which a vote already
> started. sure, SVN tags can be moved, but at least for those that
> voted
> they have already 'seen' this version in a different state and thus
> the
> new vote is prone to be inaccurate if this is not carefully done by
> the
> votee.
>
> I'd rather suggest to skip cancelled versions and bump them instead.
-1 from me as well. Not reusing versions is documented at [1]
Note that any changes to the artifacts under vote require a restart
of the process, no matter how trivial. When restarting a vote
version numbers must not be reused, since binaries might have
already been copied around.
That being said, it's pretty easy to miss, suggestions on how to
improve it are welcome.
Robert
[1]: http://sling.apache.org/documentation/development/release-manageme
nt.html#wait-for-the-results
>
> Cheers,
> Stefan
>
> On 09/11/15 12:06, "Stefan Seifert" <[email protected]> wrote:
>
> > Hi,
> >
> > Apache Sling Commons Testing 2.0.20 - 4 Issues
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12331987
> >
> > Apache Sling Commons JSON 2.0.14 - 4 Issues
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12333769
> >
> > Apache Sling Maven Sling Plugin 2.1.4 - 2 Issues
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12334045
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachesling-1
> > 365/
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1365 /tmp/sling-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] 0 Don't care
> > [ ] -1 Don't release, because ...
> >
> > This majority vote is open for at least 72 hours.
> >
> >
> > stefan
> >
>
>
