Devnotes sprint-5
Project: http://git-wip-us.apache.org/repos/asf/incubator-ignite/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-ignite/commit/f1cfd298 Tree: http://git-wip-us.apache.org/repos/asf/incubator-ignite/tree/f1cfd298 Diff: http://git-wip-us.apache.org/repos/asf/incubator-ignite/diff/f1cfd298 Branch: refs/heads/ignite-648 Commit: f1cfd2985803c8b05462737b847f956ea043341a Parents: 015afdb Author: avinogradov <avinogra...@gridgain.com> Authored: Mon Jun 8 15:17:54 2015 +0300 Committer: avinogradov <avinogra...@gridgain.com> Committed: Mon Jun 8 15:17:54 2015 +0300 ---------------------------------------------------------------------- DEVNOTES.txt | 42 +++++++++++++++++++++++++++++------------- 1 file changed, 29 insertions(+), 13 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/f1cfd298/DEVNOTES.txt ---------------------------------------------------------------------- diff --git a/DEVNOTES.txt b/DEVNOTES.txt index 1562dc4..b7fea83 100644 --- a/DEVNOTES.txt +++ b/DEVNOTES.txt @@ -24,12 +24,14 @@ NOTE: JDK version should be 1.7.0-* or >= 1.8.0-u40. Ignite Release Instructions =========================== -Use people.apache.org/keys/committer/<username>.asc key to generate KEYS file. -Execute these commands at source root: +Use your people.apache.org/keys/committer/<username>.asc key to generate KEYS file. +Download https://dist.apache.org/repos/dist/release/incubator/ignite/KEYS and append you key using commands: gpg --list-sigs <keyname> >> KEYS gpg --armor --export <keyname> >> KEYS +Upload modified KEYS file. + Specify gpg profile at settings.xml. It will be used to sign sources and artifacts. <profile> @@ -43,24 +45,38 @@ Specify gpg profile at settings.xml. It will be used to sign sources and artifac Ensure you have RELEASE (not SNAPSHOT) version at Ignite poms. Maven release plugin release:prepare goal can be used to make release tag. -Deploy Ignite release candidate to maven repository and dev-svn: +Deploy Ignite release candidate to maven repository and dev-svn, make tag: + + Following command deploys Ignite to maven repository, prepares sources and fabric edition binaries. + mvn deploy -P apache-release,gpg,release,scala,lgpl,deploy-ignite-site -Dignite.edition=fabric -DskipTests -B + + In case you want to release both fabric and hadoop editions you have to build hadoop edition first using command + mvn package -P apache-release,gpg,release,scala,lgpl -Dignite.edition=hadoop -DskipTests -B + save /target/bin/*.zip, make "mvn clean" and restore saved files before deploying fabric. - mvn deploy -P apache-release,gpg,release,scala,lgpl,deploy-ignite-site -Dignite.edition=fabric -DskipTests -B + Binary artifact name can be changed by setting additional property -Dignite.zip.pattern. Binary artifact will be + created inside /target/bin folder when release profile is used. - Binary artifact name can be changed by setting additional property -Dignite.zip.pattern. - Sources package name is fixed. Sources package zip will be created automatically when apache-release profile used. + Sources artifact name is fixed. Sources artifact will be created inside /target dir when apache-release profile is used. - In case you want to release both fabric and hadoop editions you have to build hadoop first, save /target/bin/*.zip, - make "mvn clean" and restore them before deploy step. + Nexus staging (repository.apache.org) should be closed with appropriate comment contains release version and + release candidate number, for example "Apache Ignite 1.0.0-rc7", when mvn deploy finished. - Nexus staging (repository.apache.org) should be closed when mvn deploy finished. - Checkout https://dist.apache.org/repos/dist/dev/incubator/ignite svn. Create new folder with name equals to released - version at svn root. Copy target/site folder content to svn/ignite/<version> folder and commit. + Checkout https://dist.apache.org/repos/dist/dev/incubator/ignite svn. Create release candidate folder with name + equals to release version with "-rc*" ending, for example "1.0.0-rc7", at svn root. + Copy /target/site folder content to svn/ignite/<rc-version> folder and commit with appropriate comment. -Start vote based on https://dist.apache.org/repos/dist/dev/incubator/ignite/<version>. + Make appropriate git tag for release candidate, for example "ignite-1.0.0-incubating-rc7". -Release nexus staging and copy binaries and sources from https://dist.apache.org/repos/dist/dev/incubator/ignite/<version> +Start vote based on https://dist.apache.org/repos/dist/dev/incubator/ignite/<rc-version>. + +Release nexus staging, move binaries and sources from https://dist.apache.org/repos/dist/dev/incubator/ignite/<rc-version> to https://dist.apache.org/repos/dist/release/incubator/ignite/<version> when version accepted. +Use svn mv ^/dev/incubator/ignite/<rc-version> ^/release/incubator/ignite/<version> command for proper moving. + +Make appropriate git tag for released version, for example "ignite-1.0.0-incubating". + +Send an email to d...@ignite.incubator.apache.org contains release svn url. JCache TCK compliance
