On 02/08/2007, at 5:31 AM, Dennis Lundberg wrote:

Agreed, I figured I'd just start here. I can probably change the 2's to 1's and for the rest folks can do the math :)

I assume you mean Unscheduled, not Unassigned?

Some people have given it a once over, it just needs to keep going until empty. Backlog is really for things that pre-date being diligent with JIRA :) We should aim to reduce and eventually remove it.

Hmm, do you mean need it before as in it must exist to use, or it is scheduled before 2.1?

It's currently used as things that might go into 2.1, but I've seen it look confusing because it behaves differently to 2.0.x (clearly after 2.0, where 2.0 is already released). So I'm suggesting we reverse the naming and use "2.1" for things going into 2.1, and 2.1.x for things we know will remain issues in 2.1 and will be fixed in 2.1.x. I agree that it needs to exist as a version in JIRA whenever 2.1 does.

my hope is that docs are distributed, site is not :)

I think it will be a case that users rarely care about the site, and only the docs, so they'll file in the right place. And if we can put links on all pages that say how to report an issue with that page, that'd be even better :)

But we don't have that separation yet anyway...

Sounds good. I prefer this to subtasks (which should be reserved for when a big task is composed of a set of steps that are all required to complete it).

Thanks! Brett