On 9/10/2016 2:41 PM, Andrea Pescetti wrote:
Patricia Shanahan wrote:
On 9/10/2016 12:55 PM, Ariel Constenla-Haile wrote:
only code with a bug and release blocker flag approved by the Release
Manager can be checked in that branch; that is: if you want to include
changes in the AOO413 branch:
1) open a bug
2) request releaser blocker status
3) only once the release manager approves the release blocker status,
commit your changes
Yes, this is the rule to follow. In my case, the changes I referred to
are https://bz.apache.org/ooo/show_bug.cgi?id=127103 which is an obvious
release blocker.
Andrea argues that it is traditional to put all point releases in the
same branch. Following that tradition we would use AOO410 for all 4.1.x
releases.
Correct. This is traditional but wrong (or at least awkward). So I also
agree we should change it. I'm unsure about doing it for 4.1.3, but at
latest we should change this (and communicate the change) upon releasing
4.1.3. This ensures we can consider all downstream packagers to be
informed.
I feel, very strongly, that the creation of the 4.1.4 branch should not
wait for completion of the 4.1.3 release. We should be making decisions
about 4.1.4 content, and checking in code for it, while 4.1.3 is
undergoing testing, voting, and file copying.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
