Sure, moving to JIRA would also be fine. The thrust of this proposal is
that we start using Milestones and targetting tickets towards them. The
roadmap tool we use is a minor point. Even if we switched with JIRA,
we'd still have to change how we use the ticketing system.
As for switching, I think we should either switch all or none.
Personally, I find it confusing when for a single project, some
materials are on one one site, and others on another. This applies to
the wiki thread as well. If we want to move to Confluence, then let's
get it installed on our Apache servers and move our all the wiki pages
to it. Especially as Struts expands, it is important we keep a tight
discipline of consistency for how we manage the projects.
Don
Ted Husted wrote:
Or, we could JIRA for the new projects, which supports Roadmaps directly.
* http://tinyurl.com/8m4d6
-Ted.
On 11/30/05, Don Brown <[EMAIL PROTECTED]> wrote:
I propose we use an automated, easy to understand roadmap that relies on
Bugzilla tickets marked against Milestones.
With all the action in the Struts project lately, it is hard to see what
is going on where, and specifically, qualitatively how much work remains
before a Milestone will be reached. We need a system that makes it easy
to see at a glance the roadmap of each Struts subproject, and guide new
contributions.
I see the solution involving the following:
1. All tickets, bugs and enhancements, should be marked against a
Milestone if accepted
2. Any major feature or bug fix committed to svn should have a ticket
and be assigned to a milestone.
3. A ticket should only be marked against a Milestone if a developer
has committed to work on it
4. Once all the all the tickets against a Milestone have been
resolved, the release is ready to be rolled.
The public face of this solution will be automated roadmap pages, which
will be generated from Bugzilla reports. These pages will show, at a
glance, the status of each subproject, its milestones, and current
progress toward reaching them.
I've developed a Java console app, driven by a cron, which screen
scrapes Bugzilla reports to generate a roadmap [1]. As you can see from
the demo, we don't currently use milestones much at all. The roadmap is
an idea taken from Trac [2] and I've personally have had great success
with this approach of organizing Milestones.
Comments?
Don
[1] http://www.twdata.org/dakine/roadmap/action.html
[2] http://www.edgewall.com/trac/
---------------------------------------------------------------------
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]
