Re: Call for votes: Release 3.2.1
I think the best option is to move the burden to the backport proposer. While backports serve a critical function there's good reason to make it a bit of a challenge to keep them down to the ones that are really needed. Therefore we could make the proposer responsible for (1) detecting a +3 vote on the backport and (2) doing the JIRA bookkeeping for the backport and (3) probably doing the actual commit and JIRA update. Tuesday, July 17, 2012, 8:48:37 PM, you wrote: Now a word on the process: It's PITA. I know *why* we now clone the issues in Jira, but that doesn't make it easier to actually go through all the hoops:
Re: Call for votes: Release 3.2.1
On 7/18/12 9:37 AM, Alan M. Carroll wrote: I think the best option is to move the burden to the backport proposer. While backports serve a critical function there's good reason to make it a bit of a challenge to keep them down to the ones that are really needed. Therefore we could make the proposer responsible for (1) detecting a +3 vote on the backport and (2) doing the JIRA bookkeeping for the backport and (3) probably doing the actual commit and JIRA update. +1. That's sort of how it used to work, the person suggesting a backport owns it. The release manager(s) will need to help herd the release, and everyone (yes, you!) need to get better at voting on backports. -- Leif
Re: Call for votes: Release 3.2.1
Just a reminder for myself: borrow subversion's automatic merge script. - Igor Galić iga...@apache.org wrote: Hey folks, I've added a bunch of bugs to backport for 3.2.1 http://s.apache.org/ts-3.2.1 I'd like to see some votes on this to cut and tag a release until Friday. Thanks folks! -- Igor Galić Tel: +43 (0) 664 886 22 883 Mail: i.ga...@brainsware.org URL: http://brainsware.org/ GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE -- Igor Gali? Tel: +43 (0) 664 886 22 883 Mail: i.ga...@brainsware.org URL: http://brainsware.org/ GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE
Re: Call for votes: Release 3.2.1
- Original Message - Hey folks, I've added a bunch of bugs to backport for 3.2.1 http://s.apache.org/ts-3.2.1 I'd like to see some votes on this to cut and tag a release until Friday. Hey there, I did a first bunch of backports, the results of whic you can see here; https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310963version=12321685 Now a word on the process: It's PITA. I know *why* we now clone the issues in Jira, but that doesn't make it easier to actually go through all the hoops: * Propose a patch + Jira# * Vote on it * Accept it - clone it * remove Backport for $version from old bug * now we track a different issue in STATUS or at least in CHANGES BUT, many patches include an update to CHANGES, one way or the other * change CHANGES/STATUS to reflect the new Jira# * Commit/Make sure the commit message reflects the right Jira# * Make sure you don't fuck up anywhere. * Close cloned bug with new SHA1 sum(s). I'd like to hear some feedback from someone who tries to do a couple of backports themselves. One of my ideas is that whoever adds a third +1, or moves the patches from proposed to accepted, creates the clone in jira, mangles STATUS and removes the old bug's backport. But that puts a lot of work on the some people, and might keep votes low :-S Well, that's all from me, So long, i -- Igor Galić Tel: +43 (0) 664 886 22 883 Mail: i.ga...@brainsware.org URL: http://brainsware.org/ GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE
