On 2/4/11 16:23, Alasdair Nottingham wrote:
Assuming my vote counts, something I'm not sure about since I'm not a
felix committer and I never could work out that part of the "rules"
Technically, only PMC members vote count for legal purposes, but for
something like this, I think we can use what ever definition of
consensus we want.
-> richard
On 4 February 2011 17:17, Richard S. Hall<he...@ungoverned.org> wrote:
On 2/4/11 12:10, Alasdair Nottingham wrote:
In that case I change my non-binding B vote to a non-binding A vote.
A (non-binding).
The balance has tipped...A is now ahead by two! :-o
-> richard
On 4 February 2011 16:37, Richard S. Hall<he...@ungoverned.org> wrote:
On 2/4/11 11:29, Jeremy Hughes wrote:
Just to be clear does "failed release" mean:
i) a release whose artifacts were published e.g. to apache.org/dist or
maven central then found to be bad
ii) a release that failed before the artifacts were published
I had been working to ii) but I can see there could be confusion.
Yes, (ii). This is when we call a vote, but then decide to cancel the
vote
for some reason. So the artifacts have never made it into maven central
or
apache.org/dist.
-> richard
Jeremy
On 4 February 2011 08:50, Guillaume Nodet<gno...@gmail.com> wrote:
Following the discussion, I'm starting a vote to decide on a policy
for failed releases.
[ ] A - Releases following a failed release can reuse the same version
[ ] B - Releases following a failed release must use a different
version
The vote will be opened for at least 72 hours.
Happy voting!
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
