Bernd Fondermann wrote:
So I would like to remind all honourable fellow committers to use the
"veto" powers and even the word "veto" with great care.
I'm sorry I already used veto twice for v2.3.
I never used the veto previously, but I think that it is important to
fix possible problems as soon as they happens, and not wait for a
release vote to see what the majority want.
I would have voted -1 to a release from v2.3 including that patches, so
I preferred to cast a veto and force a veto resolution early than
ignoring my concerns.
I also explained I would have retired the veto if the majority was in
favor of that patch. If it was clear to me that majoriry agreed with the
patch I wouldn't have vetoed at all. I really don't like any action that
stop development efforts.
From the ongoing vote it seems that at least Norman and Joachim shared
my concern about the first veto and I think the second one has already
been solved (Norman is really active: he already agreed with my concerns
and reverted it). If other times I used -1 outside from a vote context
then it is simply used a brief summary of the following sentence.
I really would like to have v2.3 branch ready for 2.3.1, next-minor
branch or the-name-noel-prefer for next-minor, and trunk used for
next-major until we decide to branch.
For trunk I think CTR for issues that does not break backward
compatibility is perfect.
For v2.3 I would really prefer something like this:
---
Committer Foo post a message titled "[PROPOSAL] 2.3.1 release proposal"
and saying:
"I think we need a 2.3.1 release out in X weeks because of this issue,
this issue and this. I propose to apply the following patches to the
v2.3 branch:
- updated license header
- check other legal requirements are fixed
- JIRA-XXX
- JIRA-XYZ
- r454984
Is there anything else you think should be backported?
Is there anything from this list you wouldn't backport?
"
A small discussion should show us the issues we agree upon and the one
that will need specific votes.
When consent is clear, or a majority vote passed I expect things to
happen and a vote to make the release to start and pass without problems.
---
My concern was that committers started applying patches to v2.3 without
any consent about this. I wanted to be sure people was aware of this and
the vote will make it clear what should have been done and what
shouldn't have been done.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
