Update RELEASE

This step is not typically required when you plan on continuing work in the same major release area. For example, if you just produced a 2.13.0 release and expect to continue supporting it and possibly having more 2.13.0 maintenance releases, you will likely not need to update the variables mentioned below.

You should inspect/change the value of the RELEASE, RELEASE_LAST, RELEASE_LAST_PREV and RELEASE_NEXT variables at the top of the include/data/configure.in script to their logical values.

The following assumes that you just created the 2.11.0 release and the last release published was 1.8.1.

RELEASE_LAST_PREV

This should be set to the version of the release prior to the one you just created. For example, if you just released 2.11.0 and the prior release was 1.8.1 then set RELEASE_LAST_PREV to 1.8.1.

RELEASE_LAST

This should be set to the version just released (2.11.0 in this example).

RELEASE

This should also be set to the version just released (2.11.0 in this example). This is new starting with 2.11.0 where we continue supporting the release via yum updates until the next release of Fedora.

RELEASE_NEXT

This should be a guess at what the next release will be. It will be formed by NST's major ID (2), followed by the version of Fedora we expect to base it off of. For example, if the current release is 2.11.0 (based off of Fedora 11), a reasonable guess for RELEASE_NEXT would be 2.12.0 (assuming the next release will be based off of Fedora 12).

Here are a few more variables you may need to adjust in the file:

MANIFEST_FILES

You probably won't need to change this, however, if you plan on change the number of variations of the NST to distribute, you will want to update this list (you will also need to update the release: target in include/make/makefile if you add, remove or modify your variant list).