Changes between Version 14 and Version 15 of Developer/Release

Timestamp:

11/10/16 01:21:32 (7 years ago)

Author:

Chris Johns

Comment:

--

Developer/Release

@@ -38 +38 @@
 1. RTEMS Source Builder ([https://git.rtems.org/rtems-source-builder.git git://git.rtems.org/rtems-source-builder.git])
 1. RTEMS Tools ([https://git.rtems.org/rtems-tools.git git://git.rtems.org/rtems-tools.git])
-1. RTEMS Testing Support ([https://git.rtems.org/rtems-testing.git git://git.rtems.org/rtems-testing.git])
+1. RTEMS Documentation ([https://git.rtems.org/rtems-docs.git git://git.rtems.org/rtems-docs.git])
 1. Example applications ([https://git.rtems.org/examples-v2.git git://git.rtems.org/examples-v2.git])
 1. Networking examples ([https://git.rtems.org/network-demos.git git://git.rtems.org/network-demos.git])
@@ -73 +73 @@
 
 ----
-----
 
 = Pre-Release Checklist =
@@ -89 +88 @@
   * Review contents of top of each repo for being up to date.
 
+----
+
 = Release Procedures =
 
@@ -97 +98 @@
 
 == Create a Release Branch for new Major or Minor ==
+
  1. Create branch for release, for example `git checkout -b 4.11`
  1. Follow the steps below for Create a Release Branch Release.
@@ -107 +109 @@
 
 == Create a Release Branch Release ==
+
  1. Switch to Release Branch, for example `git checkout 4.11`.
  1. Run release.sh in Dot (D) mode, for example `./release.sh -V 4.11.0 -M 4.11 -D`.
@@ -118 +121 @@
    1. RSB
 
-----
+== Releasing Process ==
 
-= Snapshot =
+1. This procedure is run and tested on FreeBSD. It uses a large amount of bandwidth and so it typically run `sync.rtems.org`.
+1. Documentation is built and this includes PDF there a valid documentation build environment is required including production quality fonts.
 
-There are no snapshots as of yet.
+Clone the [https://git.rtems.org/rtems-release/ RTEMS Release] repository and create the release providing the release's branch and the dot release number:
+
+{{{
+$ git clone git://git.rtems.org/rtems-release.git
+$ cd rtems-release
+$ ./rtems-release 4.11 0
+}}}
+
+```NOTE:``` for a release candidate use `0-rc1` as the dot release number.