Tim,
Kudos for pushing the JIRA thing through. I'm excited about this.
Question to the community. How should we treat "RESOLVED" vs "CLOSED"? In
a team bug reporting environment, the bug fixer is supposed to mark the bug
resolved and the original reporter is supposed to check it and mark it
closed. Does this work in a diverse community? Or should we just
automatically "close" bugs once a suitable testing time has passed?
Best,
WILL
----- Original Message -----
From: "Tim Colson (tcolson)" <[EMAIL PROTECTED]>
To: "Velocity Developers List" <[email protected]>
Cc: "Jeff Turner" <[EMAIL PROTECTED]>
Sent: Monday, September 12, 2005 10:44 PM
Subject: Jira maintenance
Hey gang -
So the Jira instance now has Velocity bugs in it... but it looks like
there needs to be some cleanup done. I can work on that, but want to run
stuff by here.
I asked Infra how we would request turning off Bugzilla (I didn't ask
them to turn it off, just "how".) I assume we'll want to direct people
to 'one' place for issue tracking, and that Jira will be that place very
very soon.
Hey Shinobu -- Jeff said you need to sign up for a jira account...but,
uh, I see an account in Jira, so maybe you already created it. At any
rate, I added you to the velocity-developers group.
Versions -- man, there are a lot of them. Most need to be marked as
"released", some archived, others perhaps deleted (1.0b1, 1.0b2, 1.0b3
-- a quick search, none of them seem to be associated with issues).
I assume we'll want to have 1.5 as unreleased and <1.5 marked as
released. I suggest we stick 1.6 and 2.0 in the list as well, so we can
"schedule" bugs/features/improvements for those versions and that way
the "roadmap" will be clearer for what's on tap for 1.5, 1.6 and beyond.
There are a ton of "resolved" but not "closed" issues... I'll start
looking at those too so we can get things a bit cleaned up.
Velocity Tools --> I think we should create a separate project like Jeff
suggested for "VELTOOLS" and move relevant issues over because the two
projects have separate release schedules and versions.
Cheers,
Timo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
