Kepler: Module Release Checklist

Anonymous users must enter captcha below.

Don't put anything here

Page Parameters

Don't put anything here

Page Name (for URL)

Page Title

Don't put anything here

Show Advanced Options

Don't put anything here

Page Content

This checklist describes the release process of a component assuming it has a version in the format `X.Y[.Z]`

Once a release cycle is announced in the Kepler list, most of the tasks are supposed to be executed by developers with CVS commit access. But if you want to help with the checklist, tasks that can be executed by anyone with CVS read access are marked with a "(anyone)" tag. Just make sure you use the module CVS HEAD and report any issues in the Kepler list.

1. Check merges on the module release branch and the trunk (project developers)
* Check pending bug reports and feature requests (anyone)
* Build for Linux/OSX/Windows
    1. Check the module dependencies (anyone)
    * Check the module source (anyone)
        1. Module header comments
        * Module CVS tagline
        * Module public API comments
        * _COPYRIGHT Attribute
        * _DESCRIPTION Attribute
        * _VERSION Attribute using the format `projectname X.Y.Z`
    * Check the module documentation (anyone)
        1. [[Documentation Format]]
        * Module name
        * Version
        * License
        * What's new
            * Include the CVS delta based on the sum of resource histories. You can get a full listing of deltas for the working version using [cvs2cl](http://www.red-bean.com/cvs2cl/) -t.
        * Release date
        * References to [=LuaBinaries=] and its version
        * Images (PNG, GIF)
        * Module [[Dependencies]]
            * Dependencies names, sites and versions used with this module version
        * Documentation Links
            * Links to previous versions. This may require the creation of a directory on the Kepler site and the copy of the previous files to the directory corresponding to (`http://www.keplerproject.org/projectname/X.Y`)
            * Download from [[LuaForge]] (`http://luaforge.net/projects/projectname/files`)
            * Links to Kepler Project Home (including the logos)
            * Links to the Kepler mailing list on the Contact Us section (on index.html) and on the left menu
            * Links to the Lua Site
            * Links to the module license page
            * Link to the project LuaForge sections on the left menu:
                * Project home
                * Bug Tracker
                * CVS
        * Validate XHTML and links. This can be done locally or remotely. If done remotely the files should be copied to a ''preview'' directory on (`http://www.keplerproject.org/projectname/preview`). A simple link checker can be found at [http://validator.w3.org/checklink](http://validator.w3.org/checklink)
        * README
             * Reference to the project home page
             * Version number
             * Description of the directories and files
        * Test the examples in the documentation
    * Update the Rockspec with the current version
    * Test the binary build for Windows, Linux and OSX (anyone)
        * Make sure you don't have the CVS version of the project Rock installed
        * Use `luarocks make rockspecs/projectname-X.Y.Z-V.rockspec` 
    * Test the configuration (anyone)
    * Test the installation (anyone)
    * Execute the unit tests (anyone)
* CVS details (project developers)
    * Branch using `rel_[0-9]_[0-9]_x`
    * Tag using `v[0-9]_[0-9]_[0-9]_[alpha|beta][2-9]`
* Generate the tar.gz and zip archives (using the [[Distribution Format]]) (project developers)
    * `modulename-X.Y[.Z].tar.gz`
    * `modulename-X.Y[.Z].zip`
    * `modulename-X.Y[.Z]-win32-[luaXY].zip`
* Test the tgz and zip archives. (anyone)
    * Check included files
    * Check the install/build process.
* LuaForge project details (project admin)
    * Bug Tracker
        * Categories (API, Documentation, Other)
        * Groups (Version numbers)
    * Feature Requests
        * Categories (API, Documentation, Other)
        * Groups ("Next Release")
* Upload to LuaForge (project developers)
    * Create the release `modulename-X.Y[.Z]`
    * Release and Change notes (the line breaks have to be manually positioned)
    * Source tar.gz and zip files
    * Binary zip files for Windows
* Submit the module Rockspec (project developers)
    * Update the release URL in the Rockspec
    * Generate the Rock files (`luarocks pack projectname X.Y.Z-V`)
    * Send the Rockspec to the LuaRocks list
    * Wait for the Rocks upload and confirmation
    * Test the uploaded Rocks
* Upload to the Kepler site (`ftp.keplerproject.org`) (project developers)
    * Documentation
    * Logo and images
* Links on the Kepler wiki (`www.keplerproject.org`) (anyone)
    * [[Modules]] page
    * [[Releases]] page
* Update LuaForge project page (project admin)
    * Public Info
    * Trove version and scope
* Announce the module on the Kepler list (project admin)
* Announce on the modules on LuaForge as a news post (project admin)
    * LuaForge Home Approval (LuaForge admin)
* Announce the module on the Lua list (project admin)

About this Edit

Minor Edit

Edit Summary