Note | ||
---|---|---|
| ||
This document is subject to change without notice. |
Stabilization
Minor and major number releases go through a stabilization period before release, and remain in maintenance (bugfix) mode after release. To start the release process, we create an "A.B.x" branch based on the latest trunk.
...
In these respects we are using the same release process as Subversion:
Voting
Under some circumstances, the stabilization period will be extended.
...
Core code changes, of course, require voting, and restart the soak or test period, since otherwise the change could be under-tested.
Voting
A change to the A.B.x line must be first proposed to the dev mailing list via a JIRA ticket. The rest of the voting process takes place in JIRA. The mail might look something like this: "I'm proposing to include the solution to ticket FINERACT-20045 in release 1.22.0. I'm calling on all committers and interested contributors to join the discussion there." Please don't use dev@ for the actual discussion. Conducting it in JIRA gives contributors the ability to opt out of individual discussions which don't interest them without opting out of the global FINERACT communication.
...
Here's an example, probably as complex as an entry would ever get:
Code Block | ||
---|---|---|
| ||
Summary
Make a button which reads the user's mind.
Justification:
It's what every user always wanted.
Notes:
There was consensus on the desirability of this feature.
Concerns:
Vetoed by myrle due to privacy concerns.
Votes (version A.B.x)
+1: mage, gstein
-1: myrle |
...
A change needs three +1 votes from committers and no vetoes to go into A.B.x. If non-committers would like to vote it must be made clear in the voting section that their vote is 'non-binding' as follows:
Code Block | ||
---|---|---|
| ||
Votes:
+1: danielsh, hwright
+1 (non-binding): stylesen |
...
If you cast a veto (i.e. -1), please state the reason in the concerns field, and start the discussion on the ticket. If you believe the information you are adding to the discussion is interesting for the broader community, also send a mail to dev that the issue is being discussed on ticket FINERACT-XYZ.
If you add revisions to a ticket, note that the previous voters have not voted for those revisions, as follows:
Code Block | ||
---|---|---|
| ||
Votes (version 1.2.1) |
...
+1: mage, gstein |
...
-1: myrle |
...
Votes (version 1.2.2) |
...
+1: mage |
If in case votes have been communicated by means other than comments on the JIRA ticket means, note that in the summary.
...