"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "devscripts/RELEASE-CHECKLIST" between
cheetah3-3.2.0.tar.gz and cheetah3-3.2.1.tar.gz

About: Cheetah3 is a template engine and code generation tool for e.g. for Web development or Java, SQL, LaTeX, form email ... (written in Python).

RELEASE-CHECKLIST  (cheetah3-3.2.0):RELEASE-CHECKLIST  (cheetah3-3.2.1)
0. Run full test suite in all branches. Continue if all tests passed. 0. Run full test suite in all branches. Continue if all tests passed.
1. Run ../prerelease $NEW_TAG. 1. Run devscripts/prerelease $NEW_TAG.
1a. The script checks out the release branch ('maint' for a bug-fix 1a. The script checks out the release branch ('maint' for a bug-fix
release, 'master' for minor or major release) and calls editor; update release, 'master' for minor or major release) and calls editor; update
version, the list of contributors, the list of changes and download version, the list of contributors, the list of changes and download URL
URL in ANNOUNCE.rst; if it is a stable release - edit docs/news.rst to in ANNOUNCE.rst; if it is a stable release - edit docs/news.rst to set
set release date. Edit Version.py and README.rst in the release branch release date. Edit Version.py and README.rst in the release branch -
- fix versions. Edit section [egg_info] in setup.cfg - set if it is fix versions. Edit section [egg_info] in setup.cfg - set if it is a
a stable or development release. In SetupConfig.py edit "Development stable or development release. In SetupConfig.py edit "Development
Status" in trove classifiers; edit dev_tag or download URL: if a Status" in trove classifiers; edit dev_tag or download URL: if a
non-stable version - append 'dev' and date stamp, for a stable non-stable version - append 'dev' and date stamp, for a stable version
version remove 'dev' and date stamp). Commit. Verify. remove 'dev' and date stamp). Commit. Verify.
2. Run ../prerelease-tag $NEW_TAG. This checks out the release branch and 2. Run devscripts/prerelease-tag $NEW_TAG. This checks out the release
creates the new tag at the head of the release branch. Push the branch branch and creates the new tag at the head of the release branch. Push
and the tag to start test/build. the branch and the tag to start test/build.
3. Run devscripts/release. This generates and uploads new archives to PyPI.
4. Generate new docs using devscripts/build-all-docs. Upload docs using
devscripts/publish-docs.
5. Run devscripts/postrelease. The script checks out master and null-merge
maint. The script restores ANNOUNCE.rst from the previous commit
(HEAD~). It calls editor; update next version, remove the list of
contributors and the list of changes, edit download URL in ANNOUNCE.rst.
Edit docs/news.rst - add new version. Edit Version.py and README.rst -
fix versions. Edit section [egg_info] in setup.cfg. In SetupConfig.py
edit "Development Status" in trove classifiers; edit dev_tag or download
URL. Commit. Verify. Fast-forward next to master.
3. Run ../release. This generates and uploads new archives to PyPI. 6. Run devscripts/push-all in the development repository to push all
branches and tags to the public repositories.
4. Generate new docs using ./build-all-docs. Upload docs using 7. Send announcement to the Cheetah mailing list. For a stable release send
./publish-docs. announcements to python and python-announce mailing lists.
5. Run ../postrelease. The script checks out master and null-merge maint. 8. Announce new release at Wikipedia
The script restores ANNOUNCE.rst from the previous commit (HEAD~). It
calls editor; update next version, remove the list of contributors
and the list of changes, edit download URL in ANNOUNCE.rst. Edit
docs/news.rst - add new version. Edit Version.py and README.rst - fix
versions. Edit section [egg_info] in setup.cfg. In SetupConfig.py
edit "Development Status" in trove classifiers; edit dev_tag or
download URL. Commit. Verify. Fast-forward next to master.
6. Run ../push-all in the development repository to push all branches
and tags to the public repositories.
7. Wait until tests finished at AppVeyor. Download generated wheels, put
them into dist directory and upload to PyPI using twine.
8. Send announcement to the Cheetah mailing list. For a stable release
send announcements to python and python-announce mailing lists.
9. Announce new release at Wikipedia
(https://en.wikipedia.org/wiki/CheetahTemplate). (https://en.wikipedia.org/wiki/CheetahTemplate).
 End of changes. 7 change blocks. 
33 lines changed or deleted 30 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)