Add bug numbers to revision metadata
When a commit is made, record the bug numbers the change relates to.
Blueprint information
- Status:
- Complete
- Approver:
- Mark Shuttleworth
- Priority:
- Undefined
- Drafter:
- Martin Pool
- Direction:
- Needs approval
- Assignee:
- Martin Pool
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Martin Pool
- Completed by
- Martin Pool
Related branches
Related bugs
Sprints
Whiteboard
This very important feature (to me) seems a little bit "forgotten". May I try to "resurrect" it? :)
For my needs, Bazaar would become a killer app if it proposes following option : make bug/task number a requirement at each checkout and/or checkin.
Of course Bazaar need to be linked with a task/bug repository, and must check task/bug ID and status before to allow checkout or checkin. With a GUI, task/bug ID and title can be displayed like a list or filtered list (by assignement, status, ...).
I have a very "task oriented" way of managing projects. I "need" to know :
- what have been done to solve a bug/task (all changes, and only changes related to this bug/task).
- which bug/task was the cause of a change (in code or whatever).
This is the only way to avoid commits of changes related to a set of tasks/bugs (which change for which task?), or commits not related to any task/bug.
----
@jbcrouig: This is actually now implemented: http://
There's no option at present to enforce that changes must have bug numbers, and more could be done as far as marking changes that partially fix bugs or are otherwise related to them without actually fixing them. If you'd like to talk about or work on that, please post to the list.
