summaryrefslogtreecommitdiff
path: root/CODING
diff options
context:
space:
mode:
Diffstat (limited to 'CODING')
-rw-r--r--CODING8
1 files changed, 4 insertions, 4 deletions
diff --git a/CODING b/CODING
index 8b1fed6..5438352 100644
--- a/CODING
+++ b/CODING
@@ -97,8 +97,8 @@ Tips
97Release process instructions 97Release process instructions
98============================ 98============================
99 99
100* Announce at release@lists.enlightenment.org that you are planning 100* Announce at enlightenment-release@lists.sourceforge.net and
101 for the release 101 enlightenment-devel@lists.sourceforge.net that you are planning for the release
102* Change versions in efl/__init__.py (ex: 1.9.0) 102* Change versions in efl/__init__.py (ex: 1.9.0)
103* Update the ChangeLog file: 103* Update the ChangeLog file:
104 setup.py build_doc -b changes ...and manually merge from the html file 104 setup.py build_doc -b changes ...and manually merge from the html file
@@ -106,8 +106,8 @@ Release process instructions
106* Test the generated tarballs 106* Test the generated tarballs
107* scp tarballs & md5sums to: 107* scp tarballs & md5sums to:
108 download.enlightenment.org:/srv/web/download.enlightenment.org/public_html/pre-releases/ 108 download.enlightenment.org:/srv/web/download.enlightenment.org/public_html/pre-releases/
109* Announce at release@lists.enlightenment.org that tarballs are 109* Announce at enlightenment-release@lists.sourceforge.net and
110 ready for testing 110 enlightenment-devel@lists.sourceforge.net that tarballs are ready for testing
111 111
112... wait 24 hours, fix any issues found. In the mean time you can prepare the 112... wait 24 hours, fix any issues found. In the mean time you can prepare the
113 release announcement for phame/ml. 113 release announcement for phame/ml.