I am seeing a lot of issues being assigned to 4.1. I find it unrealistic. Below is a
gentle reminder on how I'd like us to assign versions.
On 4 nov. 2011, at 11:40, Emmanuel Bernard wrote:
## Managing JIRA
JIRA is not exactly a list to Santa Claus. Let me rephrase, JIRA is not a list to Santa
Claus. You can't put a version number to a JIRA issue and hope things will magically
be fixed in this version. The rule of thumb is simple:
1. If you think you will do it, set the version number
2. If you know someone that will likely do it, put a version number
3. if it's vitally important that this be fixed in the next version, see rule #1
Otherwise don't put a version number without asking the project lead
The rule is a bit different for the project lead as he has to draw the big picture of
what a release will contain and assigning a number is the easiest solution. A corollary is
that moving a problem from version n to version n+1 is useless.
Today we ended up with 60 issues that ought to be resolved in less than a week. That
obviously is beyond our capacity.
Of course these rules are not hard enforced but we definitively need to shift back into a
more conservative version assignment management.
By the way, I don't know if you have followed AS 7's team rant on JIRA and
actionable items. While I'm not 100% inlined with their rule, I am sympathetic to the
idea of a managed flow of JIRA issues. I'm not sure how this can be applied to (or at
least get closer with) search, validator and ogm but I'm open to ideas.