Bump versions for 1.11 development

1 files changed, 9 insertions, 8 deletions

diff --git a/CODING b/CODING
index 87ea7ed..8982924 100644
--- a/CODING
+++ b/CODING
@@ -44,17 +44,19 @@ Tips
 Release process instructions
 ============================
 
-* Announce at release@lists.enlightenment.org that you are planning for the
-  release
+* Announce at enlightenment-release@lists.sourceforge.net that you are planning
+  for the release
 * Change versions in the top part of setup.py (ex: 1.9 and 1.9.0)
+* Raise efl/elm min requirements
+* Update README.rst
 * Update the changes.html file
     setup.py build_doc -b changes ...and manually merge
 * Git push and wait jenkins to generate the 2 tarballs
 * Test the generated tarballs
 * scp tarballs to
   download.enlightenment.org/srv/web/download.enlightenment.org/public_html/pre-releases
-* Announce at release@lists.enlightenment.org that tarballs are ready for
-  testing
+* Announce at enlightenment-release@lists.sourceforge.net that tarballs are
+  ready for testing
 
 ... wait 24 hours, fix any issues found. In the mean time you can prepare the
     release announcement for phame/ml.
@@ -66,10 +68,9 @@ Release process instructions
 * Create and push the branch for stable backporting
     git branch python-efl-1.9 && git push origin python-efl-1.9
 * Publish the blog post on phame (Official Announcements)
-* Announce the release to announce@lists.enlightenment.org with cc to devel
-  etc.
-* Update download link on website (clone website/www.git, edit, and use the
-  update link found in the url below)
+* Announce the release to release@lists.enlightenment.org
+  (an alias for e-announce etc.)
+* Update download link on website (clone website/www.git, edit, commit, push)
 * Change versions again in setup.py (ex: 1.10 and 1.9.99)
 * Raise efl and elementary requirements in setup.py (to 1.9.99)