On 2012-08-01 22:22, Andy Parker wrote:
It sounds like this change in process is getting a lot of support.
I've talked to a couple of the people here at Puppet Labs about it and
they are on board, too.
I think the big remaining question is how to track where the patch
needs to be applied. The master branch is a given. The ticket already
has a field for affected version and target version, but that doesn't
allow us to have multiple target versions and track them
independently.
I guess the problem I'm thinking of is one that we currently have.
Namely, in the current workflow we have "Merged - Pending Release"
which after a release of the target version changes to "Closed". We
cannot track right now (as far as I know) that it has been fixed in
2.7.x and released as 2.7.22, and fixed in 3.0.x but not yet released.
I guess we could handle that by having a ticket for each release that
is affected, but I'm a little worried about the overhead of tracking
that, but if is what is needed we can at the very least try it out.
Perhaps it's enough to mark tickets as "needs backporting" separately?
Or have a separate "Backport Status" field that goes "Unknown" ->
"Required" -> "Merged" -> "Released" or "Unknown" -> "Unnecessary".
Best Regards, David
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
