|author||Oded Gabbay <firstname.lastname@example.org>||2015-10-01 12:29:45 +0300|
|committer||Oded Gabbay <email@example.com>||2015-10-01 12:29:45 +0300|
Add RELEASING file
Signed-off-by: Oded Gabbay <firstname.lastname@example.org>
1 files changed, 44 insertions, 0 deletions
diff --git a/RELEASING b/RELEASING
new file mode 100644
@@ -0,0 +1,44 @@
+Here are the steps to follow to create a new hsakmt release:
+1) Ensure that there are no uncommitted changes or unpushed commits,
+ and that you are up to date with the latest commits in the central
+ repository. Here are a couple of useful commands:
+ git diff (no output)
+ git status (should report "nothing to commit")
+ git log master...origin (no output; note: *3* dots)
+2) Increment hsakmt (major|minor|micro) in configure.ac according to
+ the directions in that file.
+3) Make sure that new version works.
+4) Use "git commit" to record the changes made in step 2 and 3.
+5) Generate and publish the tar files by running
+ make PREV=<last version> GPGKEY=<your gpg key id> release-publish
+ If your freedesktop user name is different from your local one,
+ then also set the variable USER to your freedesktop user name.
+ make release-publish-message
+ to generate a draft release announcement. Edit it as appropriate and
+ send it to
+7) Increment hsakmt_micro to the next larger (odd) number in
+ configure.ac. Commit this change, and push all commits created
+ during this process using
+ git push
+ git push --tags
+ You must use "--tags" here; otherwise the new tag will not
+ be pushed out.