|
From: Matthieu C. <cho...@gm...> - 2011-11-20 23:37:44
|
No objection for me. Matthieu 2011/11/20 Alan Ezust <ala...@gm...> > Hello fellow devs. > > I realize I have been filling in certain roles without announcing that > they were things I felt responsible for... > > I volunteer to continue being "release owner" of 4.5.x, as I was for 4.4.x > up to the time that 4.5.x was branched. > > What is a release owner? > > http://producingoss.com/en/stabilizing-a-release.html#release-owner > > If you want to "own" 4.4.x, that means you have to use/test it and each > rev you merge. > > I decided to stop using/testing/maintaining the 4.4.x branch. Which means > any 4.4.x merge requests that are posted to the merge request tracker need > to be handled by someone else. If you want to be the release owner of > 4.4.x, and be responsible for doing the future merges and bringing a future > release of 4.4.x, let me know. If you want to volunteer and need help doing > your first couple, let me know and I can help. > > Also, I have occasionally broken some of the rules in the > release-procedure.txt with regards to changes in the non-trunk branch. My > changes have usually been quite small, things that are already in trunk, > and things I wanted to "slide into the release" before I vampire does his > release. > > Such rules should only be broken by the "release manager" of that branch, > I think. > And they should be done only with great care, to keep consistency with the > other branches, and never to add new features. > > The recent times I broke it was to add tooltips to certain often confused > menu items or options, for example. > > I didn't post a merge request and wait for it to be reviewed, because I > felt that it was a small change, something i already made to trunk, and it > didn't really need to be reviewed and approved. > > Are there any objections from other devs to me declaring myself "release > owner" of 4.5.x and continuing to work as I have been? > > > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > -- > ----------------------------------------------- > jEdit Developers' List > jEd...@li... > https://lists.sourceforge.net/lists/listinfo/jedit-devel > > |