Agree on 2.7 and love the idea for a regression label. Would be a good 'first bug' for folks new to the project to help cut support releases.
Here's a battery of queries, how do we decide we need a MINOR point release? can it be just one issue cherry picked? does it need to be fully packaged or is a tag enough? On Thu, Apr 18, 2013 at 12:48 PM, Andrew Grieve <[email protected]>wrote: > We had previously discussed creating a 2.6.1 point release that had only > stability fixes in it since 2.6.0, but no feature changes. > > Does anyone want to follow through with it for this round? I'm leaning > towards focusing all efforts on making sure 2.7.0 is extra solid since > we'll be promoting during "conference month". > > One thing I'm wondering is if it might be easier to do this if we added a > "Regression" label to all issues that we would like cherry-picked into > point releases. As of right now, we'll have to go through the commit log > and manually figure out what changes fit the category and cherry-pick them. >
