Hi,

I started working on a patch to make the Trac concept of a version
more useful. A milestone may be targeted for a version, and a version
may have a due date. There is a page to view a version, attach files
to it, and (not yet implemented) to edit a version. Viewing a version
shows the milestones targeted to it, similar to the roadmap. The
roadmap displays "For version:???" after the milestone completion.

I have tried to make the patch as non-intrusive as possible. If there
are no versions, nothing changes. If milestones are not targeted to a
version, nothing changes other than a new drop-down on the edit
milestone view.

I will probably modify the roadmap to a) group milestones by version,
b) replace targeted milestones with the versions, or c) intersperse
versions in the milestones. Possibly as a plugin/alternate view.

What I'm wondering is if anyone is interested in such a patch. Would
there be a chance of it being applied to Trac core if I finished it?

Background:
I've always been slightly annoyed that a version is only visible as a
name in tickets. There's no relation to anything else, and the
description is only visible on the admin page. At $WORK, I am trying
to replace an ancient TWiki storyboard and Bugzilla with Trac, but we
would like a two-level hierarchy for iteration/story. We've looked at
a couple plugins, but they don't work (itteco), are overly-complex
(agile-trac), or don't really fit our use-case well.

Malcolm


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to