Changes between Version 11 and Version 12 of Developer/Release


Ignore:
Timestamp:
May 14, 2015, 5:15:23 PM (4 years ago)
Author:
Gedare Bloom
Comment:

Streamline and improve release procedures.

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Release

    v11 v12  
    105105
    106106
    107 = Release Checklist =
     107= Release Procedures =
    108108
    109 Main release steps.
     109Start with either of the following two sets of instructions depending on whether creating a new Release Branch, or only a new Release Branch Release for an existing release branch. Accompany either with announcements to the website, mailing lists, and social media.
    110110
    111 == General ==
    112 
    113 
    114 == Git ==
    115  1. Create branch for release
    116 
    117 
    118 == Website ==
    119  1. Announcement
    120 
    121 
    122 == Trac ==
    123 
    124  1. Bump default version to the current release
     111== Create a Release Branch for new Major or Minor ==
     112 1. Create branch for release, for example `git checkout -b 4.11`
     113 1. Follow the steps below for Create a Release Branch Release.
     114 1. Switch back to master branch, `git checkout master`
     115 1. Create a local branch for updating the development master, for example `git checkout -b 5.0`
     116 1. Update master version numbers with release.sh in Bump (B) mode, for example `./release.sh -V 5.0.0 -M 5.0 -B`.
     117 1. Push to the master, for example `git push upstream 5.0:master`.
     118 1. Bump default version to the current release, for example 5.0. (This may have been done already.)
    125119 1. Generate 'next' milestone
    126120
    127 
    128 == FTP ==
    129  1. Upload file to FTP with sha256.
    130 
    131 
    132 == Documentation ==
    133  1. Generate docs from branch.
     121== Create a Release Branch Release ==
     122 1. Switch to Release Branch, for example `git checkout 4.11`.
     123 1. Run release.sh in Dot (D) mode, for example `./release.sh -V 4.11.0 -M 4.11 -D`.
     124 1. Check changes for correctness.
     125 1. Push Release Branch and Tags, for example `git push upstream 4.11` and `git push upstream --tags`
     126 1. Generate !ChangeLog using script found in #2208
     127 1. Upload files to FTP with sha256.
     128 1. Update https://docs.rtems.org/
    134129   1. Texinfo
    135130   1. Doxygen
    136131   1. RSB
    137  1. Update `docs.rtems.org`
    138 
    139 
    140 == Tarball Generation ==
    141  1. Run bootstrap
    142  1. Generate !ChangeLog using script found in #2208
    143132
    144133----