= Release Procedures = [[TOC(Developer/Release, depth=2)]] This page details steps that need to be taken in order to cut a release of RTEMS. = Source Checklist = The items in these lists are in no particular order and subject to discussion, additions, and deletions. The following are things that MUST be resolved before a release is made * Tools stabilized on known versions, these can be different versions if required. * If it is not possible for a tool to be built it must be well documented in the release notes. * All BSPs must build without error * Select BSPs must run tests without errors see [wiki:Developer/Release#RequiredBSPs Required BSPs] The following are things that WOULD BE NICE to be resolved before a release is branched * Warning reduction pass * Focus on all SPARC BSPs, select PowerPC, ARM and MIPS = Required BSPs and Conditions= These BSPs must build and have all tests without errors. * sparc/erc32 * ... Coverage reports for these BSPs * sparc/erc32 = Release Checklist = Main release steps. == General == == Git == 1. Create branch for release == Website == 1. Announcement == Trac == 1. Bump default version to the current release 1. Generate 'next' milestone == FTP == 1. Upload file to FTP with sha256. == Documentation == 1. Generate docs from branch. 1. Texinfo 1. Doxygen 1. RSB 1. Update `docs.rtems.org` == Tarball Generation == 1. Run bootstrap 1. Generate !ChangeLog using script found in #2208 ---- = Snapshot = There are no snapshots as of yet.