Author: intrigeri Date: To: The Tails public development discussion list Subject: Re: [Tails-dev] [Proposal] Redmine workflow simplification: drop
"Fix committed" status
Hi,
sajolida: > "Fix committed" is pretty much the same as "Resolved" from a developer's
> perspective: it means "no more work to be done". But it's very different
> from a user's perspective: "Fix committed" is not solved for users yet.
Sure.
> This might be relevant for help desk for example or to the few power
> users who actually check "the list of things that will be in the next
> release", as per /support.
Yes, we link in a few places to "the list of things that will be in
the next release". I'd like to point all these links to a Redmine
custom query that lists closed tickets with Target version = the
next release.
Would this address your concern?
Implementation-wise, the release manager will need to update this
custom query during the release process. This is cheaper and simpler
than what they currently have to do at that time, that is: mark all
"Fix committed" tickets as "Resolved", which is not as straightforward
as it may seem due to blocker relationships.
