[gbrainy] Document release process
- From: Jordi Mas <jmas src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gbrainy] Document release process
- Date: Sun, 28 Nov 2010 15:08:53 +0000 (UTC)
commit 3ecc0c15467afddc4ef3aed98a3b0502e8186f6b
Author: Jordi Mas <jmas softcatala org>
Date: Sun Nov 28 16:11:06 2010 +0100
Document release process
RELEASE-PROCESS | 26 ++++++++++++++++++++++++++
1 files changed, 26 insertions(+), 0 deletions(-)
---
diff --git a/RELEASE-PROCESS b/RELEASE-PROCESS
new file mode 100644
index 0000000..cb53548
--- /dev/null
+++ b/RELEASE-PROCESS
@@ -0,0 +1,26 @@
+Here are the steps to create a new gbrainy release:
+
+1) Send a message two weeks before the release to the gnome localization list asking translators to update gbrainy's translations
+
+2) Run all the unit tests and verify that they pass
+
+See tests/README
+
+3) Update the file NEWS with the most rellevant changes
+
+4) Make sure that the configure.ac contains the right version number for the release
+
+5) Execute make 'make distcheck' and make sure that completes correctly
+
+6) Do a smoke test to verify that gbrainy has been built properly
+
+7) Tag the gbrainy git repository naming the tag label GBRAINY_X_Y_Z, where X and Y are the major versions and Z the revision number.
+
+8) Upload the final tar.gz to a public location
+
+9) Send a message to the gnome announce list
+
+10) Update gbrainy releases page
+
+
+
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]