I’m up for sheriff duty this Thursday, and I thought I might try something that people have discussed many times. It’s a bit radical, and I’m not sure if people will like it though. The idea is to only have the sheriff push changesets. This way, the sheriff can push things at a rate he/she is comfortable with, and stay on top of all the performance charts and random oranges. If it happens to be a slow day, I’ll be going through the checkin-needed bugs and pushing those as well.
It makes sheriffing a full time job, but I think it’s worth a try to see how it works out. I also think it will be a valuable data point to determine if we want to do it like this all the time.
Feedback wanted (posting to dev.planning as well)!
2 replies on “Sheriff Duty”
I’m not sure if I like this, but if it does ensure the sheriff will watch the tree (instead of me, the committer), it /might/ be worthwhile.
The kink I am trying to comprehend is how does one go about getting a changeset to push to you, the sheriff. And does priority on what gets pushed when simply rest with your discretion, or would it apply like today, “anyone can push if tree green; unless sheriff decides we need to close/meter checkins”?
(I just caught the x-post to .planning and reposting my comment there as well)
[…] Calendar Sheriff Duty […]