On Tue, Nov 20, 2012 at 12:58:46PM -0500, Chip Childers wrote: > On Tue, Nov 20, 2012 at 12:51 PM, Alex Huang <alex.hu...@citrix.com> wrote: > > Sometime ago I suggested a process for doing this. Have we considered that > > process and decided it's not useful? I think that process is much easier > > to maintain than a list on the wiki. > > > > Here's what I posted. I realized I talked about cherry-picking but this > > process is also good for fixing bugs. > > > > "We should make use of the Jira functionalities. > > > > These steps can be performed by everyone. > > - A bug is filed in issues.apache.org/cloudstack. This should target the > > releases that it is to be fixed in. > > - If the bug needs to be propagated to another release, a subtask is > > created for that release. > > I was good with this process when you first sent it out, but then I > remembered that the fixVersion and affectsVersion fields are > multi-value. I think we need to do both. Bugs are the records that > we should put into release notes, while tasks are the tracking items > to help us understand if something is done for a particular branch. > > My only concern is that the task-based approach (as opposed to simply > using the multi-value nature of affects and fix version fields) is the > level of effort required to maintain multiple Jira records. > > Joe, do you want to give it a shot using tasks and we'll see if that's > sustainable?
Sure - I'll give it a shot and see if it works. Note that the volume for a .x release is going to be much lower than a major release - but this will give some indication how it works. -- Joe Brockmeier http://dissociatedpress.net/ Twitter: @jzb
