So the current management process in JIRA is a bit rusty, but is intended to be (as in I used to do it that way but no reason why anyone else should):
New issue comes in (Version Unscheduled) We assign it to a future version. We use 3.2 for 'yes, soon' and 3.x for 'later'. It gets done with said future version I've the urge to change that. Take this issue: https://issues.apache.org/jira/browse/LANG-903 It's a feature request. It has no patch or code. It's a great 'someone please code'. I still like the triage notion of a new issue coming in and being looked at. As it is, I'm not interested personally and so I want to put it into a 'anyone wanna code' bucket. So I'm thinking of a version called: 'Feature Request' We could also have 'Patch For Review'. We still have 2.7, 3.2 and 4.0, but we ditch the .x versions. I think that would make our backlog of issues clearer. Here's the new stuff. Here's the stuff that needs coding. Here's the stuff that needs reviewing. Here's Bucket X of other stuff (bugs? chores like fixing the site?). What do others think? Hen
