...
Configuring JIRA to track workflow for maintenance branches and releases
- Megan is working with Peter to improve our ability to track workflow in JIRA. She wanted our thoughts about this.
- Peter seems to have put a new field in place for JIRA views, called "Status for 2.4.x"
- this seems a little too specific, as you'd have to have one for each version
- it would be better to have a more generic field simply for specifying the version, which could be used for any maintenance branch
- what's really needed is to disambiguate the "Fix version(s)" field. Right now that can either mean "intended fix version" or "version where this was actually fixed," depending on whether it's been resolved or closed appropriately.
- A new field called "Intended version" or "Target version" sounds like a better answer
...
- we were initially talking about minimizing UI changes for 2.5, but now we're entertaining this pop-up idea. Is that too much?
- not really. We'll just adopt a strategy of having the new bits off by default, but available for enabling through sakai.properties or tool options
- we should, however, try to halt the scope increase now. We're only two months from the next code freeze, and still trying to work on 2.4.x issues
- we haven't yet taken on the file-picker helper issues we had earlier planned to
- the basic problem: design issues oriented around user expectations for adding attachments to things, and consistency between two different ways of adding attachments (namely, attaching by linking and attaching by copying.)
- we need to give some design attention to this, but really need to move on it fairly soon, and set some deadlines for ourselves
- still mostly looking at design issues
Proposed Deadlines for 2.5.0
- Resources tool feature freeze: July 15
- this will be for settling on the scope of any UI changes we'll consider for 2.5
- probably no more than the pop-up idea IU is floating, but we'll give ourselves a week to think it over and get additional input
- File-picker feature freeze: Aug 1
- for settling the scope of any file picker (attachment helper) changes
- need a little extra time to think through this one, as user expectations are a little murky
- we'll have a focused meeting about this next Tuesday at the same time (4 p.m. GMT, 5 p.m. BST, noon EDT, 9 a.m. PDT)
- Specification freeze*: Aug 15
- final designs/specifications for what will be completed for 2.5
- this will be surfaced to the community as what they can expect to see in the release
- Code freeze: Sept 15
- changes delivered in a working state (i.e. tested to a first order)
- String freeze: Oct 1
- we may not need this, but any message bundle work will be finalized by this point
- Branch freeze: Oct 15
- target for the release as a whole
- Release: Nov 1
...