Misc #9218
closedBranch Maintainer Appointment / Discharge Process
Description
There's a library appointment / discharge policy see ruby-core:25764 (http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/25764). There should be a similar policy for branch maintainership.
A. candidacy process
when someone offers to maintain a branch, they must also declare how long they are maintaining it for.
B. election process
looking at the candidates and recommending someone on ruby-core/ruby-dev. When elected, the new maintainer must decide and announce how long they will maintain it for.
C. discharge process
1a. declared they are not maintaining it anymore
1b. is inactive for 1+ month and a discussion takes place on ruby-core/dev
2. a new person needs to be elected like described above.
Updated by naruse (Yui NARUSE) almost 11 years ago
I think this should be follow http://bugs.ruby-lang.org/projects/ruby/wiki/MaintainerDischargingProcess
when someone offers to maintain a branch, they must also declare how long they are maintaining it for.
I doubt anyone can commit such period, and I don't believe such commitment.
Therefor the important one is discharge process or emergency release process.
Updated by zzak (zzak _) almost 11 years ago
- Category changed from Project to doc
- Status changed from Open to Assigned
- Assignee set to zzak (zzak _)
We have decided on this approval and discharge process in approx. terms.
I provide documentation for our process and encourage commercial support for EOL rubies.
We aim for a minimum 6 month discharge / EOL process.
Candidacy and election should take place on the mailing list, but this isn't always the case. The important part is discharge and communicating EOL timelines.
Updated by zzak (zzak _) almost 11 years ago
- Status changed from Assigned to Feedback
=begin
I have added the following wiki pages:
- ((<BranchMaintainerAppointmentProcess|URL:https://bugs.ruby-lang.org/projects/ruby/wiki/BranchMaintainerAppointmentProcess>))
- ((<BranchMaintainerDischargingProcess|URL:https://bugs.ruby-lang.org/projects/ruby/wiki/BranchMaintainerDischargingProcess>))
Regarding our official maintenance duration policy, this will be included in a separate document. The purpose of these pages is to only provide process for appointment and discharge of branch maintainers.
=end
Updated by zzak (zzak _) almost 11 years ago
- Status changed from Feedback to Closed
- % Done changed from 0 to 100