23 Apr
2007
23 Apr
'07
6:39 p.m.
ok I've done the move (after Nam and Sergiu gave me their go ahead).
Note that I have told jira not to send email messages as there would
have 135 of them...
The idea is that we should not put anything in the 1.1 release itself
(as we've done for the 1.0 release) as we should put stuff in 1.1
Beta 1, etc. So if there's something in "Future" that we want in 1.1
Beta 1, then we move it there. We already have a few things in 1.1 B1
which are the leftovers from 1.0 that we didn't have the time to
implement.
The goal is that things that we plan have a good chance of being done
in the version they're scheduled for.
I propose that to highlight important issues in Future we do the
following:
- increase the severity when issues are important and decrease it
when they're not important
- mark issues with patches with the "patch" keyword as we've started
doing
- use the votes to decide if an issue is important for users. We need
to encourage users to vote for their favorite issues
Last we need to decide an overall goal for the 1.1 release. I'll send
another mail for this.
Thanks
-Vincent
On Apr 23, 2007, at 11:04 AM, Vincent Massol wrote:
Hi,
We have lots of jira tasks scheduled for 1.1 but I don't think
that's right. According to our new strategy we're only scheduling
issues that we know we want to do in a given release. I think we've
used 1.1 in the past as a way to say "later". But we have "future"
for this now. So I'd like to move all the tasks in 1.1 into
"Future" if that's ok with you.
Let me know.
Note: We also need to continue moving the issues that have no "fix
for" set (unscheduled issues). There are 76 of these.
Thanks
-Vincent