>
> Is this something a PMC newbie could do? I worked with stack to document
> the process at one time.
>

This is something any committer should be able to do -- it requires write
access to git (git-wip-us.apache.org), subversion (dist.apache.org), and
nexus (repository.apache.org). PMC are required to vote on a release, but
IIRC any dev can cut a release candidate and call a VOTE thread.

> On Sep 20, 2016, at 7:19 PM, Nick Dimiduk <ndimi...@apache.org> wrote:
> >
> > Hello devs,
> >
> > I'm going on an extended absence, through Oct 23. Would anyone care to
> > stand in as release manager for 1.1.7 while I'm away? Given 1.1.6 went
> out
> > on Sept 5, 1.1.7 RC's should begin around Sept 26th in order to retain
> our
> > targeted monthly cadence. The overall process is documented [0], and I
> have
> > my own almost-but-not-quite-scripted notes [1] for creating a candidate.
> >
> > In terms of effort, it usually works out to be a couple hours for
> tracking
> > down in-flight tickets, updating JIRA, validating the compatibility
> report
> > &c, and then another couple hours of watching maven and pushing bits to
> > generate the RC.
> >
> > If no takers, I'll make its release a priority upon my return in late
> > October.
> >
> > Thanks,
> > Nick
> >
> > [0]: http://hbase.apache.org/book.html#releasing
> > [1]: https://gist.github.com/ndimiduk/924db7f5ee75baa67802
>

Reply via email to