Woot! On Thu, Jan 14, 2016 at 7:41 PM, Anthony Baker <[email protected]> wrote:
> Thanks Nitin! I updated the wiki with a few more details (and > questions). Once I get GEODE-781 merged I think all the release mechanics > are in place. > > Anthony > > > > On Jan 14, 2016, at 1:11 PM, Nitin Lamba <[email protected]> wrote: > > > > Thanks Roman, Anthony, > > > > I've added these (evolving) steps on a separate wiki page [1] and also > created the template for the announcement e-mail [2]. It may make sense to > update these pages and capture the relevant comments/ discussion there. > > > > - Nitin > > [1] https://cwiki.apache.org/confluence/display/GEODE/Release+Steps > > [2] > https://cwiki.apache.org/confluence/display/GEODE/%28Template%29+Release+Announcement > > > > ________________________________________ > > From: [email protected] <[email protected]> on behalf of Roman > Shaposhnik <[email protected]> > > Sent: Wednesday, January 13, 2016 1:25 PM > > To: [email protected] > > Subject: Re: Creating a release (was Re: releaseType?) > > > > On Wed, Jan 13, 2016 at 12:38 PM, Anthony Baker <[email protected]> > wrote: > >> Let’s review the release creation process: > >> > >> 1) git clean -fed > >> > >> 2) gradle clean build > >> > >> 3) Copy the source distribution files to > https://dist.apache.org/repos/dist/dev/incubator/geode/1.0.0-incubating.M1.RC0/ > and commit. > >> > >> Anthony-Baker-MacBook-Pro:incubator-geode abaker$ ls -l > gemfire-assembly/build/distributions/apache-geode-src-1.0.0-incubating.M1.* > >> -rw-r--r-- 1 abaker staff 10383223 Jan 13 12:04 > gemfire-assembly/build/distributions/apache-geode-src-1.0.0-incubating.M1.tar.gz > >> -rw-r--r-- 1 abaker staff 821 Jan 13 12:05 > gemfire-assembly/build/distributions/apache-geode-src-1.0.0-incubating.M1.tar.gz.asc > >> -rw-r--r-- 1 abaker staff 33 Jan 13 12:04 > gemfire-assembly/build/distributions/apache-geode-src-1.0.0-incubating.M1.tar.gz.md5 > >> -rw-r--r-- 1 abaker staff 65 Jan 13 12:04 > gemfire-assembly/build/distributions/apache-geode-src-1.0.0-incubating.M1.tar.gz.sha-256 > >> -rw-r--r-- 1 abaker staff 16575408 Jan 13 12:05 > gemfire-assembly/build/distributions/apache-geode-src-1.0.0-incubating.M1.zip > >> -rw-r--r-- 1 abaker staff 821 Jan 13 12:05 > gemfire-assembly/build/distributions/apache-geode-src-1.0.0-incubating.M1.zip.asc > >> -rw-r--r-- 1 abaker staff 33 Jan 13 12:05 > gemfire-assembly/build/distributions/apache-geode-src-1.0.0-incubating.M1.zip.md5 > >> -rw-r--r-- 1 abaker staff 65 Jan 13 12:05 > gemfire-assembly/build/distributions/apache-geode-src-1.0.0-incubating.M1.zip.sha-256 > >> > >> Is this correct? Anything missing? > > > > The above steps are correct. Of course, you're missing staging into > > Distribution SVN and Maven > > AND we still haven't clarified the version sequencing. > > > >> More Questions: > >> > >> Where do we stage maven artifacts? On > https://repository.apache.org/content/repositories/snapshots? > > > > Yup. Have you seen the step-by-step instructions on Maven staging I sent > out > > recently? > > > >> I know we only vote on source releases but where do we keep binary > convenience distributions? > >> Are these generated once the release vote passes? > > > > Actually, the community has to vote on *any* artifact that get > > released to a general > > public. The idea here is that you're not required to produce binary > convenience > > artifacts, but if you do -- you have to include them into the vote. > > Attached is a > > typical vote in a Bigtop community. You VOTE email will look very > similar. > > > >> At what point is the release tag created? > > > > The release candidate tag gets created right away. It then gets either > > moved or copied to > > reflect a release name. > > > > Thanks, > > Roman. > > > > ==================================================================== > > From: Roman Shaposhnik <[email protected]> > > To: [email protected], [email protected] > > Subject: [VOTE] Bigtop 0.7.0 RC0 > > > > > > This is the seventh release for Apache Bigtop, version 0.7.0 > > > > It fixes the following issues: > > http://s.apache.org/Pkp > > > > *** Please download, test and vote by Fri 10/25 noon PST > > > > Note that we are voting upon the source (tag): > > release-0.7.0-RC0 > > > > Source and binary files: > > > https://repository.apache.org/content/repositories/orgapachebigtop-194/org/apache/bigtop/bigtop/0.7.0/ > > > > Binary convenience artifacts: > > http://bigtop01.cloudera.org:8080/view/Releases/job/Bigtop-0.7.0/ > > > > Documentation on how to install (just make sure to adjust the repos for > 0.7.0): > > > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+install+Hadoop+distribution+from+Bigtop+0.6.0 > > > > Maven staging repo: > > > https://repository.apache.org/content/repositories/orgapachebigtop-194/ > > > > The tag to be voted upon: > > > https://git-wip-us.apache.org/repos/asf?p=bigtop.git;a=commit;h=fb628180d289335dcf95641b44482fb680f11573 > > > > Bigtop's KEYS file containing PGP keys we use to sign the release: > > http://svn.apache.org/repos/asf/bigtop/dist/KEYS > > > > Thanks, > > Roman. > > -- Greg Chase Director of Big Data Communities http://www.pivotal.io/big-data Pivotal Software http://www.pivotal.io/ 650-215-0477 @GregChase Blog: http://geekmarketing.biz/
