Edgewall Software

Changes between Version 93 and Version 94 of TracDev/ReleaseChecklist


Ignore:
Timestamp:
May 20, 2015, 7:33:49 PM (9 years ago)
Author:
Ryan J Ollos
Comment:

Reorder steps according to what is actually done.

Legend:

Unmodified
Added
Removed
Modified

  • TracDev/ReleaseChecklist

    v93 v94  
    1 = Checklist of things to do before a release
     1= Checklist of things to do for a release
    22
    33The release steps are described on this page. For more information on the roadmap and schedule leading up to a release, see the RoadMap page.
    … …  
    7979 * Check whether there are any eligible changesets that have not been merged into the branch
    8080
    81 === Create dist packages
     81=== Prepare packages
    8282
    83 // Note: be sure to use Python **2.7.9** or later on Windows //
     83==== Prerequisites
     84 * use Python **2.7.9** or later on Windows
     85 * **Babel** must be installed in the environment used to build the packages on Windows.
     86 * [https://pythonhosted.org/setuptools/history.html#id52 setuptools >= 0.8] should be used to ensure PEP-0440 compliant version identifiers.
     87 * if svn >= 1.7 is used for the checkout then [https://pypi.python.org/pypi/setuptools_subversion setuptools_subversion] must be installed.
    8488
    85    * Check out trunk (or the release branch) to a '''clean''' sandbox
    86    * Build source archives on Unix:
    87      {{{#!sh
    88      python setup.py sdist --formats=gztar,zip
    89      }}}
    90      in order to get the files in `.tar.gz` and `zip` archives, with the proper LF line endings.
    91    
    92    **The `sdist` command must be performed from a svn < 1.7 checkout**, as
    93    only the data files listed in the `.svn/entries` files are considered (that is, until [https://bitbucket.org/tarek/distribute/issue/252 distribute issue252] gets fixed). If svn >= 1.7 is used, then [https://pypi.python.org/pypi/setuptools_subversion setuptools_subversion] must be installed.
    94    * Build Windows exe installers on x86 and x64 platforms. **Babel must be installed** in the environment used to build the installers.
     89==== Create dist packages
     90 * Check out trunk (or the release branch) to a '''clean''' sandbox
     91 * Build source archives on Unix:
     92   {{{#!sh
     93   python setup.py sdist --formats=gztar,zip
     94   }}}
     95   in order to get the files in `.tar.gz` and `zip` archives, with the proper LF line endings.
     96 
     97 * Build Windows exe installers on x86 and x64 platforms.
    9598 {{{#!dos
    9699python.exe setup.py bdist_wininst
    97100}}}
    98    * Test installation on target platforms. \\
    99     * Install on a clean system. ''Remove any old Trac installation before testing.''
    100     * Smoke test:
    101      - create an environment with `trac-admin`, test it with `tracd`
    102      - upgrade an environment created with the previous release' `trac-admin`,
    103        test it with `tracd`
     101
     102==== Verify installation on target platforms
     103  * Install on a clean system. ''Remove any old Trac installation before testing.''
     104  * Smoke test:
     105   - create an environment with `trac-admin`, test it with `tracd`
     106   - upgrade an environment created with the previous release' `trac-admin`,
     107     test it with `tracd`
     108
     109==== Upload packages
     110 * //[https://packaging.python.org/en/latest/distributing.html#uploading-your-project-to-pypi Upload] the packages to [http://pypi.python.org/pypi/Trac PyPi] using Twine (*)//
     111 * Upload to http://ftp.edgewall.org/pub/trac
    104112
    105113=== Finalize the release
     114 * Test `easy_install Trac`
    106115 * Tag/copy version in subversion
     116 * Update TracDownload and [wiki:TracDev/ReleaseNotes/1.1#DevelopmentReleases]
    107117 * Close release coordination ticket (e.g. #9077) (*)
    108118 * Mark the finished milestones as //completed// (with the //completed date// preferably being the date that the releases were announced), and change their descriptions from //next// maintenance/development release to //latest// maintenance/development release.
    … …  
    111121   * Attach copy of translations statistics chart of Transifex to the milestones.
    112122 * Add [/admin/ticket/versions Version] entries for the new releases (*)
    113  * Upload to http://ftp.edgewall.org/pub/trac
    114  * Update TracDownload and [wiki:TracDev/ReleaseNotes/1.1#DevelopmentReleases]
    115  * //[https://packaging.python.org/en/latest/distributing.html#uploading-your-project-to-pypi Upload] the packages to [http://pypi.python.org/pypi/Trac PyPi] using Twine (*)//
    116  * Test `easy_install Trac`
     123
     124=== Announce the release
    117125 * Post to the following channels:
    118126  * [gforum:trac-users], [gforum:trac-dev] (all releases)
    … …  
    123131}}}
    124132 * Update the versions on the [wikipedia:trac Wikipedia] page.
    125 
    126 //(*) not for beta or rc releases//
    127133
    128134=== Prepare for development
    … …  
    135141 * Update the [ReleaseTesting#Currenttargetreleases Current target releases].
    136142
     143//(*) not for beta or rc releases//
     144
    137145----
    138146See also: ReleaseTesting, RoadMap, TracDev