[3f628a]: doc / cheatsheets / making_a_release  Maximize  Restore  History

Download this file

127 lines (88 with data), 3.6 kB

All code/doc changes should be committed.

To get the svn revision of the previous release:

    $ svn log https://pyke.svn.sourceforge.net/svnroot/pyke/tags

Do "svn log" to see what's changed:

    $ svn log -r 48:HEAD https://pyke.svn.sourceforge.net/svnroot/pyke/trunk

Write: RELEASE_NOTES-0.2

FILES TO CHANGE:
    - README
        Read through to see if anything has changed.  The following lines
        will always change:
        - line  3: Version: 0.2
        - line 23:     pyke_doc_html-0.2.tar.gz
        - line 55:     pyke-0.2-py2.5.egg
        - line 63:     pyke-0.2.tar.gz
        - line 68: Add any new examples
        - line 73:     pyke_examples-0.2.tar.gz
    - setup.py
        - line 11:     version = "0.2",
    - pyke/__init__.py
        - line 3: version = '0.2'
    - doc/source/index.txt
        - line 43: Release 0.2

COMMIT SVN UPDATES

REBUILD DOCUMENTS

    $ cd doc/source
    $ bin/gen_html

REBUILD compiler_bc.py

    $ cd ../../pyke/krb_compiler
    $ python
    >>> from pyke import krb_compiler
    >>> krb_compiler.compile_krb('compiler', 'compiled_krb', 'compiled_krb', 'compiler.krb')
    $ mv compiled_krb/compiler_bc.py .

COMMIT SVN UPDATES

BUILD RELEASE

    $ cd ../..
    $ rm -rf build
    $ python setup.py bdist_egg sdist
    $ python2.6 setup.py bdist_egg
    $ ./make_doc_tarball dist/pyke_doc_html-0.2.tar.gz
    $ ./make_examples_tarball dist/pyke_examples-0.2.tar.gz

TAG RELEASE

    $ svn copy https://pyke.svn.sourceforge.net/svnroot/pyke/trunk \
               https://pyke.svn.sourceforge.net/svnroot/pyke/tags/0.2

ADD NEW RELEASE TO SOURCEFORGE TRACKERS:

    Project Admin -> Feature Settings -> Manage (on Tracker line)

    Do: Bugs, Support Requests, and Patches

    Add release through "Add/Update Groups"

UPLOAD NEW DOCUMENTATION TO SOURCEFORGE

    see web.upload cheatsheet

UPLOAD DIST FILES TO SOURCEFORGE:

    In the browser, go to: https://frs.sourceforge.net/webupload and upload
    the 5 files:
                pyke-0.4-py2.5.egg 
                pyke-0.4-py2.6.egg 
                pyke-0.4.tar.gz
                pyke_doc_html-0.4.tar.gz
                pyke_examples-0.4.tar.gz

    Go to: Project Admin -> Feature Settings
                         -> Manage (on File Release System line)
    Click on "Add Release", Enter: 0.2
    Click "Preserve my pre-formatted text." on the Release Notes (upload the
        RELEASE_NOTES-0.4 file).
    Follow the rest of the instructions there...
        After you've selected the files to include, you have to go through
        settings for each file ONE AT A TIME.  (Each file has its own Update
        button which erases any information you've entered for subsequent
        files).

        Pick "Platform Independant" for all of the files.

        Pick ".zip" for the .egg files.
        Pick "Source .gz" for the source .gz file.
        Pick ".gz" for the doc .gz file.
        Pick ".gz" for the examples .gz file.


CHECK THE FOLLOWING LINK (in setup.py):

    http://sourceforge.net/project/showfiles.php?group_id=207724&package_id=248795
    It should show the new release and the new release files.

UPDATE PYPI LINK:

    $ python setup.py register

CREATE NEWS ANNOUNCEMENTS

    On Sourceforge: Project Admin -> Feature Settings
                                  -> Submit (on Project News line)

    On Google Groups: http://groups.google.com/group/pyke

TO TEST:

    $ cd ~/python
    $ virtualenv --no-site-packages pyketest
    $ cd pyketest
    $ bash
    $ unset PYTHONPATH
    $ source bin/activate