summaryrefslogtreecommitdiff
path: root/RELEASING.txt
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2016-06-01 17:13:27 -0400
committerChris McDonough <chrism@plope.com>2016-06-01 17:13:27 -0400
commit3e9a737500e79a6a919ce53db9557c75d874b84c (patch)
treeef674c176ab29b9dede8a8fa70c3a18a26edde44 /RELEASING.txt
parentb5f065906f75efdcc9f80d4f0b8b4092e92b41c0 (diff)
parent382f93e2bfec5563587e306fda3fd34759314300 (diff)
downloadpyramid-3e9a737500e79a6a919ce53db9557c75d874b84c.tar.gz
pyramid-3e9a737500e79a6a919ce53db9557c75d874b84c.tar.bz2
pyramid-3e9a737500e79a6a919ce53db9557c75d874b84c.zip
Merge branch 'master' of github.com:Pylons/pyramid
Diffstat (limited to 'RELEASING.txt')
-rw-r--r--RELEASING.txt82
1 files changed, 67 insertions, 15 deletions
diff --git a/RELEASING.txt b/RELEASING.txt
index 866fff305..d8572fa94 100644
--- a/RELEASING.txt
+++ b/RELEASING.txt
@@ -6,12 +6,19 @@ Releasing Pyramid
- Alpha, beta, dev and similar statuses do not qualify whether a release is
major or minor. The term "pre-release" means alpha, beta, or dev.
+ - A release is final when it is no longer pre-release.
+
- A *major* release is where the first number either before or after the
first dot increases. Examples: 1.6 to 1.7a1, or 1.8 to 2.0.
- A *minor* or *bug fix* release is where the number after the second dot
increases. Example: 1.6 to 1.6.1.
+Prepare new release branch
+--------------------------
+
+- Create a new release branch, incrementing the version number.
+
- Do any necessary branch merges (e.g., master to branch, branch to master).
- On release branch:
@@ -26,14 +33,16 @@ Releasing Pyramid
- Run tests on Windows if feasible.
-- Make sure all scaffold tests pass (Py 2.7, 3.3, 3.4, 3.5, pypy, and pypy3 on
- UNIX; this doesn't work on Windows):
+- Make sure all scaffold tests pass (Py 2.7, 3.3, 3.4, 3.5, and pypy on UNIX;
+ this doesn't work on Windows):
$ ./scaffoldtests.sh
- Ensure all features of the release are documented (audit CHANGES.txt or
communicate with contributors).
+- Change CHANGES.txt heading to reflect the new version number.
+
- Copy relevant changes (delta bug fixes) from CHANGES.txt to
docs/whatsnew-X.X (if it's a major release). Minor releases should
include a link under "Bug Fix Releases" to the minor feature
@@ -52,10 +61,7 @@ Releasing Pyramid
branch, and previously released branch. Also in the previously released
branch only, uncomment the sections to enable pylons_sphinx_latesturl.
-- Change setup.py version to the new version number on both master and the new
- branch.
-
-- Change CHANGES.txt heading to reflect the new version number.
+- Change setup.py version to the release version number.
- Make sure PyPI long description renders (requires ``collective.dist``
installed into your Python)::
@@ -70,6 +76,38 @@ Releasing Pyramid
$ python setup.py sdist bdist_wheel
$ twine upload dist/pyramid-X.X-*
+- Configure RTD to publish the new release version of the docs.
+
+Prepare master for further development (major releases only)
+------------------------------------------------------------
+
+- Checkout master.
+
+- In CHANGES.txt, preserve headings but clear out content. Add heading
+ "unreleased" for the version number.
+
+- From the release branch, forward port the changes in CHANGES.txt to
+ HISTORY.txt.
+
+- In contributing.md, forward port branch descriptions from release branch.
+
+- In docs/conf.py, add a commented line under
+ pylons_sphinx_latesturl_pagename_overrides for the release.
+
+- Change setup.py version to the next version number.
+
+Update previous version (final releases only)
+---------------------------------------------
+
+- In docs/conf.py, update values under html_theme_options for in_progress and
+ outdated. Uncomment the sections to enable pylons_sphinx_latesturl.
+
+- Configure RTD to point the "latest" alias to the new release version of the
+ docs.
+
+Marketing and communications
+----------------------------
+
- Edit Pylons/pylonshq/templates/home/home.mako.
- Edit Pylons/pylonshq/templates/home/inside.rst for major releases only.
@@ -82,15 +120,28 @@ Releasing Pyramid
- Edit `http://wiki.python.org/moin/WebFrameworks
<http://wiki.python.org/moin/WebFrameworks>`_.
-- Publish new version of docs.
+- Announce to Twitter.
-- Announce to maillist.
+```
+Pyramid 1.x released.
-- Announce to Twitter.
+PyPI
+https://pypi.python.org/pypi/pyramid/1.x
+
+=== One time only for new version, first pre-release ===
+What's New
+http://docs.pylonsproject.org/projects/pyramid/en/1.X-branch/whatsnew-1.X.html
+=== For all subsequent pre-releases ===
+Changes
+http://docs.pylonsproject.org/projects/pyramid/en/1.X-branch/changes.html#version-yyyy-mm-dd
-Announcement template
-----------------------
+Issues
+https://github.com/Pylons/pyramid/issues
+```
+
+- Announce to maillist.
+```
Pyramid 1.X.X has been released.
Here are the changes:
@@ -98,19 +149,20 @@ Here are the changes:
<<changes>>
A "What's New In Pyramid 1.X" document exists at
-http://docs.pylonsproject.org/projects/pyramid/1.X/whatsnew-1.X.html .
+http://docs.pylonsproject.org/projects/pyramid/1.X-branch/whatsnew-1.X.html .
You will be able to see the 1.X release documentation (across all
alphas and betas, as well as when it eventually gets to final release)
-at http://docs.pylonsproject.org/projects/pyramid/1.X/ .
+at http://docs.pylonsproject.org/projects/pyramid/1.X-branch/ .
You can install it via PyPI:
- easy_install Pyramid==1.X
+ pip install Pyramid==1.X
Enjoy, and please report any issues you find to the issue tracker at
https://github.com/Pylons/pyramid/issues
Thanks!
-- C
+- Pyramid core developers
+```