> If it wasn’t clear when to call the vote, then that’s a topic worth
> improving on for the next release.  One suggestion would be for folks to
> unofficially vote with a -1, 0, or +1 in the discuss thread so RM can know
> where they stand.

It's time to call the vote when the RM thinks it's time to call the
vote. There should not be a vote on when it's time to hold a vote. We
should also avoid spending a lot of time trying to reach consensus
before the actual vote. The vote is the vote.

I have been thinking about this ever since I decided to be the RM for
the next SDK release. What I will try to do in the next few weeks is
to move slowly but surely towards the vote. Step by step. At each
point the community gets the chance to participate, but after a
certain deadline, the window for that particular step closes.

First, we're going to make sure all features and fixes to the code
base are in. Then we're going to make the CI builds from the release
branch available for testing, as well as run Mustella on the release
branch daily. No more features or fixes are accepted after this point.
Next up is the documentation. I'll be asking Alex and Justin by name
to spend time on this. If they clear the docs - and only then, as the
docs tend to cause the most 'extra' RCs, we move on to the final step,
the testing of the artifacts: signatures, rat, etc. Once I get an OK
on all these blocking points - or, as 'binding' when I'm RM, no
response at all - I will create an RC to vote upon. This vote will be
very strict. By this I mean that any issues raised that are not
blocker will be deferred to the next release and that any vetoes will
have to have a pretty convincing argument as well as a reason why it
wasn't raised as an issue during the

Done this way, my idea is that there will be no surprises and that
there will be a linear progression towards the release. The process
will probably take a bit longer than an 'ideal' multi-RC release (like
we've ever seen one of those ;-)), but I think it will be a lot less
effort and a lot less discussion.

Here's to hoping ...

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Reply via email to