http://www.apache.org/dev/release-publishing.html#release_manager
*"The common practice at Apache is for a single individual to take responsibility for the mechanics of a release. That individual is called the 'release manager.' Release managers take care of shepherding a release from an initial community consensus to make it to final distribution.Release managers do the work of pushing out releases. However, release managers are not ultimately responsible. The PMC in general, and the PMC chair in particular (as an officer of the Foundation) is responsible for compliance with requirements.Any committer may serve as the manager of a release.A release starts when the project community agrees to make a release. However, no release manager can make a valid release unless the community has taken the necessary steps to prepare in advance. The source code and build process must comply with the legal and intellectual property requirements for a valid release, and the project must have the infrastructure in place to correctly sign the release artifacts."* Is it important to be a committer to be a release manager? On Wed, Sep 9, 2015 at 6:31 PM, Greg Chase <[email protected]> wrote: > Nitin was a great product manager at Pivotal. Lets see if he still has his > mojo :) > > On Wed, Sep 9, 2015 at 5:34 PM, Roman Shaposhnik <[email protected]> > wrote: > > > On Mon, Sep 7, 2015 at 12:39 PM, Anthony Baker <[email protected]> > wrote: > > > As Justin mentioned, we need to make progress towards our first Geode > > release. > > > If we define that initial release as an alpha-quality artifact that we > > can rapidly iterate on, > > > we can narrow the scope down to just GEODE-77 (and perhaps GEODE-18). > > > > > > Are there other issues we need to address? > > > > GEODE-77 is obviously a hard blocker and so is GEODE-18 (and whatever > > sub tasks that may generate). The rest -- I'd say push it out of the > > release. > > > > > I suggest we use the JIRA roadmap feature to organize and track > progress > > towards > > > this release. We can the version from 1.0.0-incubating to > > 1.0.0-incubating-alpha.1 > > > given this approach. > > > > Yup. That's a good way of tracking release mechanics. > > > > One last thing missing is a release manager. Personally, seeing the > > traffic of the > > past week or so, I'm wondering if Nitin Lamba could be an ideal candidate > > to > > drive this release. > > > > He's my nomination. What do you guys think? Any other nominations? > > > > Thanks, > > Roman. > > >
