Koha/misc/release_notes
Jonathan Druart da6fde55dd Bug 20818: Add missing QA Manager entry in 18.05.00 release notes
Signed-off-by: Jonathan Druart <jonathan.druart@bugs.koha-community.org>

Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
2018-05-29 14:05:31 +00:00
..
README.txt
release_notes_3_2_0.txt
release_notes_3_4_0.txt
release_notes_3_6_0.txt
release_notes_3_8_0.txt
release_notes_3_10_0.txt
release_notes_3_12_0.txt Update release notes for final 3.12.00 release 2013-05-19 17:57:26 -04:00
release_notes_3_14_0.txt release notes for Koha 3.14.0 2013-11-21 01:40:18 +00:00
release_notes_3_16_0.txt update release notes for 3.16.0 (human) 2014-05-22 20:16:25 +00:00
release_notes_3_18_0.txt Release notes for 3.18.0 2014-11-28 13:01:16 -03:00
release_notes_3_20_0.txt Release notes for 3.20 2015-05-22 12:44:35 -03:00
release_notes_3_22_0.txt Bug 16106 Correct loose to lose in comment 2016-03-22 01:47:53 +00:00
release_notes_16_5_0.md Release Notes for 16.05.00 2016-05-26 19:09:36 +00:00
release_notes_16_11_00.md Add release notes for the 16.11.00 release 2016-11-22 17:45:41 +00:00
release_notes_17_05_00.html Add release notes for Koha 17.05 2017-05-30 03:14:40 +00:00
release_notes_17_05_00.md Add release notes for Koha 17.05 2017-05-30 03:14:40 +00:00
release_notes_17_11_00.html Add release notes for Koha 17.11 2017-11-28 14:52:13 -03:00
release_notes_17_11_00.md Add release notes for Koha 17.11 2017-11-28 14:52:13 -03:00
release_notes_18_05_00.html Bug 20818: Add missing QA Manager entry in 18.05.00 release notes 2018-05-29 14:05:31 +00:00
release_notes_18_05_00.md Bug 20818: Add missing QA Manager entry in 18.05.00 release notes 2018-05-29 14:05:31 +00:00
release_notes_22RC1.txt
release_notes_22RC2.txt
release_notes_22RC3.txt
release_notes_22RC4.txt
release_notes_22RC5.txt
release_notes_191.txt
release_notes_192.txt
release_notes_193.txt
release_notes_200pre1.txt
release_notes_200pre2.txt
release_notes_200pre3.txt
release_notes_200pre4.txt
release_notes_200pre5.txt
release_notes_200RC1.txt
release_notes_200RC2.txt
release_notes_200RC3.txt
release_notes_200RC4.txt Bug 17681: Exiisting typos might thow some feees when recieved 2016-12-16 11:29:33 +00:00
release_notes_210.txt
release_notes_211.txt
release_notes_212.txt
release_notes_213.txt
release_notes_220.txt
release_notes_221.txt
release_notes_222.txt Bug 18554: Adjust a few typos including responsability 2017-05-09 21:03:22 +00:00
release_notes_223.txt Bug 18554: Adjust a few typos including responsability 2017-05-09 21:03:22 +00:00
release_notes_30000.txt
release_notes_30000alpha.txt
release_notes_30000beta.txt
release_notes_30000stableRC1.txt
release_notes_30001.txt
release_notes_30002.txt
release_notes_30003.txt
release_notes_30004.txt
release_notes_30005.txt

How to build a Koha release -- list of reminders for RMs

Update and document the translations
 ./update.pl will update all translations and you can check for
 failed ones (a copy of the previous version of the po file is
 stored with a ~ (tilda) sign after it, so any that don't have that
 didn't succeed

Install and test the translations
 ./translate install will install every translation in the po dir

Upload the translations to translate.koha.org
 This is generally done by deleting the database and importing
 the po files using the import tool as part of kartouche

Update the release notes (look at git logs for
major improvements)

Alter the VERSION string in Makefile.PL and comment
out VERSION_FROM. For instance:
 				VERSION     => '3.00.00-stable',
               #VERSION_FROM => 'kohaversion.pl',

run perl Makefile.PL and then make manifest tardist

Sign, MD5 the release, upload:
 put the tarball its own dir
 run the following

 $ md5sum * >koha-3.00.00-alpha.tar.gz.MD5
 $ gpg --clearsign koha-3.00.00-alpha.tar.gz.MD5
 $ cat koha-3.00.00-alpha.tar.gz.MD5.asc
 $ gpg --detach-sign koha-3.00.00-alpha.tar.gz
 $ scp * download.koha-community.org

Tag the Release:
From a clone of the RM repo, run:

 $ git tag -a -m "version 3.00.00 beta" v3.00.00-beta
 $ git push --tags

From the gitweb repo, issue:

 $ git fetch --tags

 * update the website, trigger the change
 * email the list