[Framework-Team] 3.2 Release Manager
Greetings Framework Team: I was following the thread re: Plone 3.2 release, and I volunteered to help manage this release. After getting no replies, I asked in #plone and got the response (from limi) that this team choses the release manager, and that some kind of track record is expected. This is understandable. Before I make my case, the reason I didn't simply say I'll do it! is because I'd like to know a little bit more about the job. This is what I was really asking for. I certainly don't want to volunteer for something I cannot do :) So, I asked what the job entails. Is it very code-centric or more process-oriented? To me, it seems this job is about making sure that the appropriate parties are providing the pieces required for the release (cutting releases/making eggs), compiling everything, running tests, communicating with everyone on this and other teams, tagging releases, managing changelogs, building consensus about versions/features/direction, etc. Basically managing the release. Maybe I'm totally off-base. Either way, I'd like to learn. Now to make my case, and explain why *I* of all people would volunteer for this. First, it seems that this, of all releases, is the 'easiest' in a while if I read everyone's ideas correctly; that this would be only be a move to an egg buildout-based install, some bugfixes and nothing more. To me, this seems like a good opportunity for someone like myself to get involved and learn more about the process. I have been using and learning more and more about eggs/buildouts/omelettes/etc lately, and will only continue to do more in the coming year. Also, I think that this is a great opportunity to expand the pool of people available to do such work in the future. I know from my experiences in the community over the years, that this is a challenging job, and it seems like some new blood might be a good investment. Finally, I have the time and energy, and want to be more directly involved in Plone itself, rather than just a cheerleader/consumer. I already work closely with the membership team, although is basically a quarterly commitment. Sure, I don't have a proven track record working on this specifically, but I *do* have a proven track record of working with the Plone community, building consensus, prodding and driving folks to get things done, as well as attention to detail and good communication skills. So, I'd like to talk about it with the team. Sure, maybe I'm not the right person for the job, and if that's the consensus, so be it. Why would I try to do a job I'm sure to fail at? But maybe there is room for someone to mentor me, or for me to assist in the back-n-forth, communication, or grunt work? I'm willing to learn and open to ideas and suggestions. You gotta start somewhere, right...but you can't do it alone either. ~Spanky ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: 3.2 Release Manager
Martin Aspeli wrote: Helge Tesdal wrote: On 24. jun. 2008, at 22:45, Spanky wrote: Before I make my case, the reason I didn't simply say I'll do it! is because I'd like to know a little bit more about the job. This is what I was really asking for. I certainly don't want to volunteer for something I cannot do :) So, I asked what the job entails. Is it very code-centric or more process-oriented? To me, it seems this job is about making sure that the appropriate parties are providing the pieces required for the release (cutting releases/making eggs), compiling everything, running tests, communicating with everyone on this and other teams, tagging releases, managing changelogs, building consensus about versions/features/direction, etc. Basically managing the release. Maybe I'm totally off-base. Either way, I'd like to learn. Saying no to people trying to get new features into bugfix releases, even though it's unpopular decisions, and even if it's limi who really wants to. ;) /me is familiar with saying no ;) Or optilude. :-) Other useful things that Wichert has done: - setting realistic deadlines - harassing people to meet said deadlines - reading code in checkins I would request help with this because I won't always full grasp the impact of certain code changes, although I do read collective.cvs and plone.cvs to keep up with what's happening. - complaining when checkins break our policies - updating/soliciting release notes - owning the stability of a release by setting appropriate standards and performing final testing All of this sounds in line with my expectations of the job :) Cheers, Martin ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: 3.2 Release Manager
Martin Aspeli wrote: That said, I think there is a lot to be said for having the same release manager for the whole 3.x cycle, from a continuity and stability perspective. +1 ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: 3.2 Release Manager
Raphael Ritz wrote: Martijn Pieters wrote: On Wed, Jun 25, 2008 at 9:43 AM, Martin Aspeli [EMAIL PROTECTED] wrote: As far as I know I'm still release manager for 3.x. I've been waiting for the foundation board (in the person of that same limi) to answer some questions I asked about the release manager stipend. Once those have been answered I'll start planning a 3.2 release. The only reason I said anything was due to this sentence: We need to agree on actually doing that release and find a release manager for it. @Wichert So, no mal-intent :) And I agree that you've done a great job. I'm really glad Spanky's showing so much enthusiasm and willingness to do an important job. That said, I think there is a lot to be said for having the same release manager for the whole 3.x cycle, from a continuity and stability perspective. I must say that I agree with that sentiment, especially in light of what a great job Wichert has done so far. I'm in favour of not changing a winning formula. ;-) I'm probably missing something but I was quite surprised by this discussion coming up now. I would also very much prefer Wichert to continue for the Plone 3.x line if at all possible. Maybe there is a way for Spanky to get on board for Plone 4 by helping Wichert and thereby being trained on the job? I would love to shadow Wichert and help him with anything along the way. What I *dont'* want is to slow anybody down. @Spanky: please don't get this wrong. I very much appreciate your willingness to take on such an important task. None taken, I agree with everyone :) Raphael ~Spanky standing by... ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
