There is certainly no need to vote again, all that is needed is to
repost the result thus (here is all the text, but as you called the vote
it would make sense for you to post it and to cc [EMAIL PROTECTED]:
----
Release jcs trunk as 1.3.0:
+1 binding:
Aaron Smuts
Henning Schmiedehausen
Scott Eade
Thomas Vandahl
+1 non-binding:
Hanson Char
Tim Cronin
Vote passes, releasing begins.
Aaron
----
In terms of process, it would have been good to have an RC first, though
we know of course that you are brute testing the trunk every day :-)
I suggest you cut 1.3.0 to svn, as you have been doing (though after the
release is completed we should try and not do these any more) - this
will provide something for us voters to download and QA while the true
release is being prepared.
There is a tonne of stuff relating to releases at:
http://www.apache.org/dev/#releases - if you get stuck let Henning know
(off-list) - I will try and help too, but Henning has had _way_ more
practice than me.
Scott
Aaron Smuts wrote:
Too much (unknown) process for me. I have no idea who
are binding and non-binding voters, or even the
difference. . . . Please point me to a page
describing the steps one should take and the manner in
which a release vote can be held, so I can do it right
(next time). I absolutely cannot stand dealing with
inexplict process and to make things absolutely clear
I will not play catch up for long. But if you point
the way I'll follow the steps. Since we already held
the vote (AGAIN) since it wasn't clear how to follow
the proecss the first time, I would have appreciated
having being made aware of the expected steps prior to
entering the voting process for the second time.
Aaron
--- Martin van den Bemt <[EMAIL PROTECTED]> wrote:
Normally there is a VOTE RESULT which lists all the
names, so it is easy to track the vote without
having to read the entire thread. Also differentiate
in binding (people on the PMC) and non binding
votes.
Assuming this was a community/developer vote to see
if everyone supports the release, make the
release (or do an RC so people can check if
everything is ok for them), have an official vote on
the
release (with giving people the ability to check the
deliverables that you created) and release it
to the public.
The binding votes on a release need to at least be 3
+1's. In this case Henning, you and Scott. (I
didn't vote, since I don't know much about JCS)
Don't forget to cc the vote result to the PMC list
:)
Mvgr,
Martin
Aaron Smuts wrote:
Good news.
The results are in. We will release JCS 1.3.0.
We had at least six +1's and no votes against.
What are the next steps?
Aaron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
