|
Size: 2485
Comment: add some details about useful step to take when you are a goatlender.
|
← Revision 17 as of 2017-12-27 05:39:13 ⇥
Size: 2542
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| <<Include(A:dev)>> | <<Include(A:historic)>> |
| 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.mercurial-scm.org/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]] |
| Line 28: | Line 28: |
| * check [[http://hgbuildbot.kublai.com/waterfall|buildbot status]] | * check [[http://buildbot.mercurial-scm.org/waterfall|buildbot status]] |
| Line 37: | Line 37: |
| /!\ The rotation is currently suspended. |
|
| Line 41: | Line 43: |
| When you become a Goatlender, make sure that you: | When you become a Goatlender, consider: |
| Line 43: | Line 45: |
| * subscribe to both mercurial-devel@selenic.com and mercurial@selenic.com (the user mailing list), | * subscribe to both mercurial-devel@mercurial-scm.org and mercurial@mercurial-scm.org (the user mailing list), |
| Line 59: | Line 61: |
| * |
Goaltender
Note:
This page is no longer relevant but is kept for historical purposes.
Priorities for managing daily Mercurial project tasks.
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
3. Schedule
![/!\](/moin-static/modernized/img/alert.png "/!\"){kind=small}
The rotation is currently suspended.
4. Setup
When you become a Goatlender, consider:
subscribe to both mercurial-devel@mercurial-scm.org and mercurial@mercurial-scm.org (the user mailing list),
- are tracking activity of the bugzilla user on the bugtracker to track all activity automatically,
- are subscribed to all wiki update.
5. Notes
Journal of notable fact to pass the next goaltender
5.1. 2015 Week 42 (oct 12)
- durin42 is working on a new changegroup format that can transfer treemanifests
- indygreg is working on formalizing the format of streaming clones so it's more generally useful
These two topics have in common a need to interact with (and possibly extend) repository store requirements during initial clone. This is currently unsupported.
- sid0 is working on some merge driver stuff, meandering towards more in-memory operations
- foozy had more work on transaction sanity. It looked like it was starting to wind down.