7 Check the following issue filters:
9 * [Pending backports](https://dev.icinga.org/projects/i2/issues?query_id=41)
10 * [Invalid target version](https://dev.icinga.org/projects/i2/issues?query_id=55)
17 The script creates a new branch 'auto-merged-2.5.2' which is based on the
18 current support branch. It then merges all commits from the 'master' branch which
19 reference a ticket for the version that was specified.
21 If there are any merge commits you will need to manually fix them and continue the
22 rebase until no commits are left:
24 $ git rebase --continue
26 After finishing the rebase the branch needs to be merged into the support branch:
28 $ git checkout support/2.5
29 $ git merge --ff-only auto-merged-2.5.2
33 Update the [.mailmap](.mailmap) and [AUTHORS](AUTHORS) files:
36 $ git log --use-mailmap | grep ^Author: | cut -f2- -d' ' | sort | uniq > AUTHORS
40 Update the version number in the following files:
42 * [icinga2.spec]: Version: (.*)
43 * [icinga2.nuspec]: <version>(.*)</version>
44 * [tools/chocolateyInstall.ps1]: Icinga2-v(.*)-{x86,x86_64}.msi
48 Update the [ChangeLog](ChangeLog), [doc/1-about.md](doc/1-about.md) files using
49 the changelog.py script. Also generate HTML for the wordpress release announcement.
53 $ ./changelog.py -V 2.5.0
57 $ ./changelog.py -V 2.5.0 -l
61 $ ./changelog.py -V 2.5.0 -H -l
65 Commit these changes to the "master" branch:
67 $ git commit -v -a -m "Release version <VERSION>"
69 For minor releases: Cherry-pick this commit into the "support" branch.
71 Create a signed tag (tags/v<VERSION>) on the "master" branch (for major
72 releases) or the "support" branch (for minor releases).
76 $ git tag -u EE8E0720 -m "Version <VERSION>" v<VERSION>
80 $ git tag -u D14A1F16 -m "Version <VERSION>" v<VERSION>
86 For major releases: Create a new "support" branch:
89 $ git checkout -b support/2.5
90 $ git push -u origin support/2.5
92 For minor releases: Push the support branch, cherry-pick the release commit
93 into master and merge the support branch:
95 $ git push -u origin support/2.5
97 $ git cherry-pick support/2.5
98 $ git merge --strategy=ours support/2.5
99 $ git push origin master
101 # External Dependencies
105 * Update Git tags for the release jobs.
106 * Build the newly created Git tag for Debian/RHEL/SuSE.
107 * Build the newly created Git tag for Windows.
111 * Test DB IDO with MySQL and PostgreSQL.
112 * Provision the vagrant boxes and test the release packages.
113 * Test the [setup wizard](http://packages.icinga.org/windows/) inside a Windows VM.
115 * Start a new docker container and install/run icinga2.
119 $ docker run -ti centos:latest bash
121 # yum -y install http://packages.icinga.org/epel/7/release/noarch/icinga-rpm-release-7-1.el7.centos.noarch.rpm
122 # yum -y install icinga2
125 # systemctl start icinga2
126 # tail -f /var/log/icinga2/icinga2.log
130 Create a new release for the newly created Git tag.
131 https://github.com/Icinga/icinga2/releases
135 Navigate to the git repository on your Windows box which
136 already has chocolatey installed. Pull/checkout the release.
138 Create the nupkg package:
142 Install the created icinga2 package locally:
144 choco install icinga2 -version 2.5.2 -fdv "%cd%" -source "'%cd%;https://chocolatey.org/api/v2/'"
146 Upload the package to [chocolatey](https://chocolatey.org/packages/upload).
148 ## Online Documentation
150 SSH into the web box, navigate into `icinga2-latest/module/icinga2`
151 and pull the current support branch.
155 * Create a new blog post on www.icinga.org/blog
156 * Send announcement mail to icinga-announce@lists.icinga.org
157 * Social media: [Twitter](https://twitter.com/icinga), [Facebook](https://www.facebook.com/icinga), [G+](http://plus.google.com/+icinga), [Xing](https://www.xing.com/communities/groups/icinga-da4b-1060043), [LinkedIn](https://www.linkedin.com/groups/Icinga-1921830/about)
158 * Update IRC channel topic
162 * Add new minor version
163 * Close the released version
164 * Update Redmine filters for the next major/minor version