On 8/19/06, Paul Benedict <[EMAIL PROTECTED]> wrote:
1) I'd like to delete versions "1.0.0 Final" and "1.0.1 Final". There are no bugs logged >against them, because the real 1.0.0 and 1.0.1 bugs are under -- not surpringsly -- versions "1.0.0" and "1.0.1". Those are the real deal with "Final"
just being some sort of
ancient leftover. Does anyone object to deleting them?
Why can't we just archive them?
2) I put into archive mode any versions with RC and Beta. This means that users will not be able to select those versions when creating a defect. That's fine
because they are not
even downloadable anymore 3) I put any non-GA releases of the 1.2 branch also in archive mode. Should this also be done for 1.3 versions prior to 1.3.5? 4) Why do we have Family versions?
The notion is that we want to ballpark when we might consider an enhancement. The idea is that it is something that we are slating for the 1.3.x series or the 1.4.x series or 1.5.x series. In Struts 2.x, we have a Struts 2.x FUTURE. Before long we might want to break that down to a 2.0.x FUTURE and a 2.1.x FUTURE (or 3.x FUTURE), which would correspond to what we were doing in Bugzilla with the "families". We do the same thing at my day-job. We find it helpful for long-range planning when JIRA is the primary roadmapping tool. We know about when we would want to do it, but haven't picked a particular iteration (or milestone) yet. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
