Hi devs, It’s been a pain to find the next Release Manager lately so I discussed with other committers and here’s what we would like to propose: Proposal ======== * We have a list of declared Release Managers. This list would start with the following persons: - enygma - evalica - gdelhumeau - mflorea - tmortagne - vmassol If any other existing committers are willing to help the project and become a Release Manager please reply to this thread! That would help the project for sure :) Actually when new committers are added to the project we should ask them if they’d be willing to do releases. * If at any point a committer not in the Release Manager list would like to do a release, he’s more than welcome to do it! * We take turns, following the initial order. When a newcomer is added he's inserted at the bottom of the list. * If a committer cannot do the release for a reason or another (sick, holiday, workload, etc) he’s still responsible for the release and he/she needs to find a replacement. He also has the option to propose changing the release date but that needs to be accepted by the project. If he/she finds a replacement, it’s up to them to decide together who will do the release the next time that replacement’s time comes. * All releases are included (milestones, RCs, final, bugfix releases). * We switch RM at each release (be it a milestone, RC, final or bugfix release). * We put the RM list, order and upcoming releases on http://dev.xwiki.org/xwiki/bin/view/Community/ReleaseManagerRoster Bootstrapping ============= * We have 3 releases to do with some volunteers already: - 13th of Oct: 5.3M1 - Not defined - 15th of Oct: 6.2.2 - Vincent - 5.4.6 (no date defined AFAIK but ASAP) - Guillaume * Thus I propose to start with the following: - vmassol - 6.2.2 - gdelhumeau - 5.4.6 - tmortagne - 6.3M1 - enygma - following release (not known yet - 6.3M2, 6.2.3 or 5.4.7) - evalica - following release (not known yet) - mflorea - following release (not known yet) - vmassol - following release (not known yet) - ... I propose that we try this and fine-tune as we progress. Let me know if you agree or disagree. Thanks -Vincent PS: This is not a vote since I feel that only the person in the list should have a say on this since they’re the one who are going to do the hard work for the moment so it would be bad form for other committers to vote on this if they don’t participate ;) They can still voice their opinion of course... _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi devs, It’s been a pain to find the next Release Manager lately so I discussed with other committers and here’s what we would like to propose: Proposal ======== * We have a list of declared Release Managers. This list would start with the following persons: - enygma - evalica - gdelhumeau - mflorea - tmortagne - vmassol If any other existing committers are willing to help the project and become a Release Manager please reply to this thread! That would help the project for sure :) Actually when new committers are added to the project we should ask them if they’d be willing to do releases. * If at any point a committer not in the Release Manager list would like to do a release, he’s more than welcome to do it! * We take turns, following the initial order. When a newcomer is added he's inserted at the bottom of the list. * If a committer cannot do the release for a reason or another (sick, holiday, workload, etc) he’s still responsible for the release and he/she needs to find a replacement. He also has the option to propose changing the release date but that needs to be accepted by the project. If he/she finds a replacement, it’s up to them to decide together who will do the release the next time that replacement’s time comes. * All releases are included (milestones, RCs, final, bugfix releases). * We switch RM at each release (be it a milestone, RC, final or bugfix release). * We put the RM list, order and upcoming releases on http://dev.xwiki.org/xwiki/bin/view/Community/ReleaseManagerRoster Bootstrapping ============= * We have 3 releases to do with some volunteers already: - 13th of Oct: 5.3M1 - Not defined - 15th of Oct: 6.2.2 - Vincent - 5.4.6 (no date defined AFAIK but ASAP) - Guillaume * Thus I propose to start with the following: - vmassol - 6.2.2 - gdelhumeau - 5.4.6 - tmortagne - 6.3M1 - enygma - following release (not known yet - 6.3M2, 6.2.3 or 5.4.7) - evalica - following release (not known yet) - mflorea - following release (not known yet) - vmassol - following release (not known yet) - ... I propose that we try this and fine-tune as we progress. Let me know if you agree or disagree. Thanks -Vincent PS: This is not a vote since I feel that only the person in the list should have a say on this since they’re the one who are going to do the hard work for the moment so it would be bad form for other committers to vote on this if they don’t participate ;) They can still voice their opinion of course... _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi devs, It’s been a pain to find the next Release Manager lately so I discussed with other committers and here’s what we would like to propose: Proposal ======== * We have a list of declared Release Managers. This list would start with the following persons: - enygma - evalica - gdelhumeau - mflorea - tmortagne - vmassol If any other existing committers are willing to help the project and become a Release Manager please reply to this thread! That would help the project for sure :) Actually when new committers are added to the project we should ask them if they’d be willing to do releases. * If at any point a committer not in the Release Manager list would like to do a release, he’s more than welcome to do it! * We take turns, following the initial order. When a newcomer is added he's inserted at the bottom of the list. * If a committer cannot do the release for a reason or another (sick, holiday, workload, etc) he’s still responsible for the release and he/she needs to find a replacement. He also has the option to propose changing the release date but that needs to be accepted by the project. If he/she finds a replacement, it’s up to them to decide together who will do the release the next time that replacement’s time comes. * All releases are included (milestones, RCs, final, bugfix releases). * We switch RM at each release (be it a milestone, RC, final or bugfix release). * We put the RM list, order and upcoming releases on http://dev.xwiki.org/xwiki/bin/view/Community/ReleaseManagerRoster Bootstrapping ============= * We have 3 releases to do with some volunteers already: - 13th of Oct: 5.3M1 - Not defined - 15th of Oct: 6.2.2 - Vincent - 5.4.6 (no date defined AFAIK but ASAP) - Guillaume * Thus I propose to start with the following: - vmassol - 6.2.2 - gdelhumeau - 5.4.6 - tmortagne - 6.3M1 - enygma - following release (not known yet - 6.3M2, 6.2.3 or 5.4.7) - evalica - following release (not known yet) - mflorea - following release (not known yet) - vmassol - following release (not known yet) - ... I propose that we try this and fine-tune as we progress. Let me know if you agree or disagree. Thanks -Vincent PS: This is not a vote since I feel that only the person in the list should have a say on this since they’re the one who are going to do the hard work for the moment so it would be bad form for other committers to vote on this if they don’t participate ;) They can still voice their opinion of course...