|
Size: 1318
Comment:
|
Size: 1317
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 22: | Line 22: |
| * [[http://bz.selenic.com/buglist.cgi?j_top=OR&f1=bug_status&list_id=6219&o1=equals&resolution=---&o2=equals&query_format=advanced&f2=priority&bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=NEED_EXAMPLE&bug_status=IN_PROGRESS&bug_status=TESTING&v1=UNCONFIRMED&v2=URGENT||bug triage]] | * [[http://bz.selenic.com/buglist.cgi?j_top=OR&f1=bug_status&list_id=6219&o1=equals&resolution=---&o2=equals&query_format=advanced&f2=priority&bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=NEED_EXAMPLE&bug_status=IN_PROGRESS&bug_status=TESTING&v1=UNCONFIRMED&v2=URGENT|bug triage]] |
Goaltender
Note:
This page is primarily intended for developers of Mercurial.
Priorities for managing daily Mercurial project tasks.
Contents
1. Rationale
In the interest of reducing mpm's workload and spreading responsibilities, we're going to experiment with occasional rotations of people filling his daily roles. Hopefully this will increase the project's capacity and let mpm do some coding.
2. Priorities
In descending priority order:
- make sure queued messages are accepted/rejected
- whitelist legitimate posters
- drop spam, reject recruiter mail
- appropriately categorize unconfirmed bugs
- with special attention to possible regressions
- cc relevant/guilty parties
- ask for missing data, set NEED_EXAMPLE as necessary
- look for interesting issues on the user mailing list
- check buildbot status
- patch review
- sync from other repos
- review patches, in priority order
- test
- push