ignite-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sboi...@apache.org
Subject [46/50] incubator-ignite git commit: ignite-756
Date Thu, 16 Apr 2015 09:50:04 GMT
ignite-756


Project: http://git-wip-us.apache.org/repos/asf/incubator-ignite/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-ignite/commit/b417eab0
Tree: http://git-wip-us.apache.org/repos/asf/incubator-ignite/tree/b417eab0
Diff: http://git-wip-us.apache.org/repos/asf/incubator-ignite/diff/b417eab0

Branch: refs/heads/ignite-424
Commit: b417eab0069613fc031eeaad1db13e1ee9b4293a
Parents: 56aec5f
Author: avinogradov <avinogradov@gridgain.com>
Authored: Wed Apr 15 19:26:19 2015 +0300
Committer: avinogradov <avinogradov@gridgain.com>
Committed: Wed Apr 15 19:26:19 2015 +0300

----------------------------------------------------------------------
 DEVNOTES.txt | 49 +++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 49 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-ignite/blob/b417eab0/DEVNOTES.txt
----------------------------------------------------------------------
diff --git a/DEVNOTES.txt b/DEVNOTES.txt
index 1a6bd82..82f6492 100644
--- a/DEVNOTES.txt
+++ b/DEVNOTES.txt
@@ -22,6 +22,55 @@ Look for incubator-ignite-<version>-bin.zip in ./target/bin directory.
 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:
+
+gpg --list-sigs <keyname> >> KEYS
+gpg --armor --export <keyname> >> KEYS
+
+Specify gpg profile at settings.xml. It will be used to sign sources and artifacts.
+
+<profile>
+   <id>gpg</id>
+   <properties>
+      <gpg.keyname>keyname</gpg.keyname>
+      <gpg.passphrase>passphrase</gpg.passphrase>
+   </properties>
+</profile>
+
+Configure access to people.apache.org/~<username>. In necessary upload sources to site.
+See https://blogs.apache.org/infra/entry/committer_shell_access_to_people for details.
+Specify ignite-site server at settings.xml.
+
+<server>
+   <id>ignite-site</id>
+   <username>username</username>
+   <privateKey>/home/username.ppk</privateKey>
+   <passphrase>passphrase</passphrase>
+</server>
+
+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 to maven repository and site:
+
+mvn deploy -P apache-release,gpg,release,scala,lgpl,deploy-ignite-site -Dignite.edition=fabric
-DskipTests -Dignite.site=scp://people.apache.org:/home/<username>/public_html -B
+
+You might need to allow connection to people.apache.org. Just do following at console:
+
+ssh people.apache.org
+
+and type "yes" + enter.
+
+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.
+
+Start vote based on people.apache.org/~<username>/ignite-version.
+Close nexus staging when version accepted.
+
+
 JCache TCK compliance
 ======================
 To test compliance with JCache TCK use:


Mime
View raw message