Skip to content

Commit d17134e

Browse files
prateekmjagadish-v0
authored andcommitted
Updated RELEASE instructions.
Author: Prateek Maheshwari <pmaheshwari@apache.org> Reviewers: Jagadish <jagadish@apache.org> Closes apache#783 from prateekm/release-docs
1 parent 3f9bbb0 commit d17134e

File tree

1 file changed

+19
-28
lines changed

1 file changed

+19
-28
lines changed

RELEASE.md

Lines changed: 19 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -50,20 +50,34 @@ Alternatively, you can make a fresh clone of the repository to a separate direct
5050
git clone http://git-wip-us.apache.org/repos/asf/samza.git samza-release
5151
cd samza-release
5252

53-
Then build the tarball:
53+
Then build the source and samza-tools tarballs:
5454

55-
./gradlew clean sourceRelease
55+
./gradlew clean sourceRelease && ./gradlew releaseToolsTarGz
5656

57-
Then sign it:
57+
Then sign them:
5858

5959
gpg --sign --armor --detach-sig ./build/distribution/source/apache-samza-*.tgz
60+
gpg --sign --armor --detach-sig ./samza-tools/build/distributions/samza-tools-*.tgz
61+
62+
Create MD5 signatures:
6063

61-
Create MD5 signature:
6264
gpg --print-md MD5 ./build/distribution/source/apache-samza-*.tgz > ./build/distribution/source/apache-samza-*.tgz.md5
65+
gpg --print-md MD5 ./samza-tools/build/distributions/samza-tools-*.tgz > ./samza-tools/build/distributions/samza-tools-*.tgz.md5
6366

64-
Create SHA1 signature:
67+
Create SHA1 signatures:
6568

6669
gpg --print-md SHA1 ./build/distribution/source/apache-samza-*.tgz > ./build/distribution/source/apache-samza-*.tgz.sha1
70+
gpg --print-md SHA1 ./samza-tools/build/distributions/samza-tools-*.tgz > ./samza-tools/build/distributions/samza-tools-*.tgz.sha1
71+
72+
Upload the build artifacts to your Apache home directory:
73+
74+
sftp <apache-username>@home.apache.org
75+
cd public_html
76+
mkdir samza-$VERSION-rc0
77+
cd samza-$VERSION-rc0
78+
put ./build/distribution/source/apache-samza-$VERSION-src.* .
79+
put ./samza-tools/build/distributions/samza-tools-$VERSION.* .
80+
bye
6781

6882
Make a signed git tag for the release candidate:
6983

@@ -73,22 +87,6 @@ Push the release tag to remote repository:
7387

7488
git push origin release-$VERSION-rc0
7589

76-
Build the tarball for samza-tool:
77-
78-
./gradlew releaseToolsTarGz
79-
80-
Then sign it:
81-
82-
gpg --sign --armor --detach-sig ./samza-tools/build/distributions/samza-tools-*.tgz
83-
84-
Create MD5 signature:
85-
86-
gpg --print-md MD5 ./samza-tools/build/distributions/samza-tools-*.tgz > ./samza-tools/build/distributions/samza-tools-*.tgz.md5
87-
88-
Create SHA1 signature:
89-
90-
gpg --print-md SHA1 ./build/distribution/source/apache-samza-*.tgz > ./build/distribution/source/apache-samza-*.tgz.sha1
91-
9290
Edit `$HOME/.gradle/gradle.properties` and add your GPG key information (without the comments):
9391

9492
signing.keyId=01234567 # Your GPG key ID, as 8 hex digits
@@ -116,13 +114,6 @@ repository just created, and close it. This may take a minute or so. When it
116114
finishes, the UI shows a staging repository URL. This can be used in a project
117115
that depends on Samza, to test the release candidate.
118116

119-
Upload the build artifacts to your Apache home directory:
120-
sftp <username>@home.apache.org
121-
mkdir samza-$VERSION-rc0
122-
cd samza-$VERSION-rc0
123-
put ./build/distribution/source/apache-samza-* .
124-
put ./samza-tools/build/distributions/samza-tools-* .
125-
bye
126117

127118
If the VOTE has successfully passed on the release candidate, you can log in to the
128119
[repository web interface](https://repository.apache.org) (same as above) and "release"

0 commit comments

Comments
 (0)