Opened 15 years ago
Last modified 14 years ago
#9263 new enhancement
if SVN is used, milestone should manage/allowtoassign links for branch and tag
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | low | Milestone: | next-major-releases |
Component: | roadmap | Version: | |
Severity: | normal | Keywords: | custom fields tracobject |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
The history of milestones is a history of SVN release tags on different branches here.
After years or months when I look into the history of milestones I need to know what SVN branch and tag the milestone actually was.
One could say, add a note in the milestone description but I'd prefer if the creation/closing of a milestone offers to set the branch and tag information. And also displays it in the same way as the date information.
I used your search engine to find out if it was already desired but haven't found such wish.
Attachments (0)
Change History (6)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
That is why I wrote "if SVN is used". But if SVN is used, I suppose it's the common way to understand milestones as releases and releases are usually tagged and branched in projects chained in a software production cycle.
Of course, both special links would just act like a reminder to set them. Although I can image one could let base a tree view of the roadmap on it, a tree like the SVN trunk and its branches…
follow-up: 5 comment:3 by , 15 years ago
Another idea could be to modify commit-hook scripts — in the same spirit as for automatic ticket updates — to recognize statements in commit messages, e.g., "closes milestone:xyz", and do some proper adjustments of targeted milestone descriptions.
That should cover the case even for Mercurial et.al.
comment:4 by , 15 years ago
Summary: | if SVN is used, milestone should allow to assign a branch and tag to it → if SVN is used, milestone should manage/allowtoassign links for branch and tag |
---|
comment:5 by , 15 years ago
Replying to mrelbe:
Another idea could be to modify commit-hook scripts — in the same spirit as for automatic ticket updates — to recognize statements in commit messages, e.g., "closes milestone:xyz", and do some proper adjustments of targeted milestone descriptions.
This can be done in a plugin, using the IRepositoryChangeListener
interface.
comment:6 by , 14 years ago
Keywords: | custom fields tracobject added |
---|---|
Milestone: | → next-major-0.1X |
Priority: | normal → low |
This feature could easily be implemented by supporting custom fields for milestones.
This is tied very closely to one way of using milestones, which is not necessarily everyone's use. I would say that adding the relevant links to the milestone description is both sufficient and much more flexible.
Suggesting worksforme.