On Fri, Sep 9, 2011 at 1:46 PM, Roy T. Fielding <[email protected]> wrote: > On Sep 9, 2011, at 11:08 AM, Eli Collins wrote: >> The release manager - not the developers - are responsible for and >> have the final say as to what patches get merge to their branch. > > That is simply false. At no time is any individual responsible for > any part of Apache subversion, no matter how obscure the branch. > No RM has the final say on anything other than their own work.
It seems hard for an RM to be the final authority of what makes it into a release w/o also being the final authority on what patches get merged into the branch they're trying to drive a release from. Thanks, Eli > That is, they can choose not to produce a release candidate. > Furthermore, at no time whatsoever does any person "own" the job > of being RM -- there can be five active RMs on a single branch, > each producing release candidates based on what is in subversion > at the particular time that they decide to tag and build. > >> If the RM wants all this work they need to either corral the developers >> to do the merging or do the merging themselves. In short, it's their >> responsibility to get people to invest in the branch. > > That is true of anyone, on or off the PMC -- not just the RM. > > ....Roy > >
