Merge lp://qastaging/~dpb/tarmac/set-milestone-2 into lp://qastaging/tarmac
Status: | Merged |
---|---|
Approved by: | dobey |
Approved revision: | 441 |
Merged at revision: | 432 |
Proposed branch: | lp://qastaging/~dpb/tarmac/set-milestone-2 |
Merge into: | lp://qastaging/tarmac |
Diff against target: |
477 lines (+381/-3) 5 files modified
docs/introduction.txt (+16/-0) tarmac/plugins/__init__.py (+18/-0) tarmac/plugins/bugresolver.py (+106/-0) tarmac/plugins/tests/test_bugresolver.py (+196/-3) tarmac/plugins/tests/test_tarmac_plugin.py (+45/-0) |
To merge this branch: | bzr merge lp://qastaging/~dpb/tarmac/set-milestone-2 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
dobey | Approve | ||
Chad Smith | Approve | ||
Данило Шеган (community) | Approve | ||
Review via email:
|
Commit message
Add an option to bugresolver to set the milestone if not already set.
Description of the change
When resolving a bug, set the milestone if not already set.
Milestone is selected using the following algorithm:
1) nearest milestone with target date in the future
2) if no milestones are in the future, sort remaining open milestones lexically by name and pick the first
3) If all milestones have dates and we are past all dates, pick the newest of those.
4) override all that logic with a config setting of "default_milestone" which is the specific milestone name to use (which will even select a non-active milestone).
This behavior only engages if the config setting 'set_milestone = True" is present in your config file.
You can test with: trial -j4 tarmac (or ./run-tests)
Read "Hacking" for a small list of deps needed for testing.
Can you please file bugs for new features, and link them? You'll also need to set the commit message.