Difference between revisions of "Update RELEASE"
From NST Wiki
Jump to navigationJump to search| Line 1: | Line 1: | ||
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. | 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. | ||
| − | + | If necessary, you should change the value of the RELEASE and/or RELEASE_LAST variables at the top of the include/data/configure.in script to their logical values. | |
| − | The following assumes that you just | + | The following assumes that you just published a ''2.13.0'' release and are now planning on moving to a Fedora 15 base. |
| − | |||
| − | |||
| − | |||
; RELEASE_LAST | ; RELEASE_LAST | ||
| − | : This should be set to the version just released (''2. | + | : This should be set to the version just released (''2.13.0'' in this example). |
; RELEASE | ; RELEASE | ||
| − | : This should also be set to the version | + | : This should also be set to the version you will now be working on. Since, in this example, we are moving to a Fedora 15 base, it should be set to ''2.15.0''. Had we decided to continue using Fedora 13 as the base, it would be left at ''2.13.0''. |
| − | |||
| − | |||
| − | |||
Revision as of 14:49, 25 January 2011
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.
If necessary, you should change the value of the RELEASE and/or RELEASE_LAST variables at the top of the include/data/configure.in script to their logical values.
The following assumes that you just published a 2.13.0 release and are now planning on moving to a Fedora 15 base.
- RELEASE_LAST
- This should be set to the version just released (2.13.0 in this example).
- RELEASE
- This should also be set to the version you will now be working on. Since, in this example, we are moving to a Fedora 15 base, it should be set to 2.15.0. Had we decided to continue using Fedora 13 as the base, it would be left at 2.13.0.
