| 1 |
Preparations for a release: |
| 2 |
|
| 3 |
1.) Make a release branch in SVN, e.g. |
| 4 |
http://svn.code.sf.net/p/codeblocks/code/branches/release-20.xx |
| 5 |
|
| 6 |
2.) Adopt the RELEASE #define in: |
| 7 |
[C::B]\src\src\appglobals.h |
| 8 |
...and remove the comment. |
| 9 |
|
| 10 |
3.) Feel free to adopt or add a new logo in e.g.: |
| 11 |
[C::B]\src\src\resources\images\splash_20xx.png |
| 12 |
|
| 13 |
4.) With respect to changes (if any) in the logo, adopt: |
| 14 |
[C::B]\src\src\splashscreen.cpp |
| 15 |
if needed. |
| 16 |
Especially have an eye on the positions of text overlays in: |
| 17 |
DrawReleaseInfo(wxDC& dc) |
| 18 |
Check if it works, also for SAFE-MODE (start C::B w/ safe-mode option). |
| 19 |
|
| 20 |
5.) Make relevant changes in specific files, set new version number in: |
| 21 |
[C::B]\codeblocks.plist.in |
| 22 |
[C::B]\codeblocks.spec.in <- careful here: don't change the changelog |
| 23 |
[C::B]\codeblocks.spec.fedora.in <- careful here: don't change the changelog |
| 24 |
[C::B]\README |
| 25 |
[C::B]\update_revision.sh |
| 26 |
[C::B]\debian\get-orig-source |
| 27 |
[C::B]\debian\get-orig-source-from-svn |
| 28 |
[C::B]\src\build_tools\Info.plist |
| 29 |
[C::B]\src\src\resources\resources.rc |
| 30 |
[C::B]src\plugins\codecompletion\codecompletion.doxy |
| 31 |
[C::B]src\plugins\contrib\wxSmith\wxs.doxy |
| 32 |
[C::B]src\sdk.doxy |
| 33 |
|
| 34 |
5.1.) Make sure the SVN_REVISION entry in revision.m4 includes only the version number |
| 35 |
and no svn revisions (contrary to what the name implies). This is required for |
| 36 |
proper work of make dist. |
| 37 |
|
| 38 |
5.2.) Add a release entry in the debian change log, so the generated packages could |
| 39 |
have the proper version numbers. |
| 40 |
|
| 41 |
5.3.) Remove .svn.%{_svnrev} from the version variables in the .spec.in files. |
| 42 |
|
| 43 |
6.) Probably update year in footer of: |
| 44 |
[C::B]\src\src\resources\start_here\start_here.html |
| 45 |
|
| 46 |
7.) Create nightlies based on that branch and fix bugs in that branch |
| 47 |
(No new features!) |
| 48 |
Make sure to merge from trunk or into trunk, if needed. |
| 49 |
|
| 50 |
8.) After release, probably merge back relevant final changes from the |
| 51 |
branch into trunk excluding those related to release #defines and |
| 52 |
alike. (But including logos etc. if not yet done.) |
| 53 |
|
| 54 |
9.) After release, rename the branch to the date C::B was actually released, e.g.: |
| 55 |
branches/release-20.xx -> branches/release-24.12 |