Difference between revisions of "KTp/ReleaseProcess"
m (Drdanz moved page Real-Time Communication and Collaboration/ReleaseProcess to KTp/ReleaseProcess: As discussed at IRC meeting Real-Time_Communication_and_Collaboration is too long, we are moving all our pages to KTp)
Revision as of 00:31, 10 November 2012
$ for i in ktp-* telepathy-logger-qt; do cd $i; git fetch origin; git checkout master; git merge origin/master; cd ..; done
- Verify that the repository has a COPYING file in the top level directory with the correct license.
- Verify that cmake/modules/COPYING-CMAKE-SCRIPTS exists.
- Verify that all the files have a proper license header and that their license is that of the COPYING file or a compatible one:
$ git clone git://anonscm.debian.org/users/modax/copyright-helper.git $ cd copyright-helper
And for each repository:
$ ./copyright-helper.pl -sc -l ../path/to/repository
mck182's lazy approach (requires lots of scrolling and paying good attention):
$ for i in ktp-* telepathy-logger-qt; do cd copyright-helper; ./copyright-helper.pl -sc -l ../$i/; cd ..; done
Verify version numbers
- Manual process for the moment...
- REALLY IMPORTANT! For common-internals and tp-logger-qt (and any other library that is used out of its own repo) make sure to bump the SONAME if the library is no longer binary compatible with the previous version.
- It is also a good idea to keep an eye on Messages.sh and whether the .pot files have correct names and/or they are loaded properly by the code.
$ for i in ktp-* telepathy-logger-qt; do cd $i; mkdir bcheck; cd bcheck; cmake .. >>../../buildlog 2>&1; make -j4 >>../../buildlog 2>&1; echo "$i: $?"; cd ..; rm -rf bcheck; cd ..; done
This assumes that you have the latest libraries (common-internals, logger-qt) installed in the system as well. The output will show "repo: 0" if it compiled sucessfully and anything other than 0 if it didn't. The buildlog is saved in the current directory.
Create new branches
$ for i in ktp-* telepathy-logger-qt; do cd $i; git checkout -b kde-telepathy-0.4; cd ..; done $ for i in ktp-* telepathy-logger-qt; do cd $i; git push origin kde-telepathy-0.4; cd ..; done
Clone the scripts
$ git clone git://git.collabora.co.uk/git/user/gkiagia/createtarball.git $ cd createtarball $ git checkout -b changes origin/changes
Edit telepathy_config.ini to reflect the changes
- Bump versions (they should match the name of the tag, without the leading 'v')
- Add new repositories
- Verify the .po file names are correct, according to http://websvn.kde.org/trunk/l10n-kde4/templates/messages/extragear-network/ - note that if the .pot file matches the name of the repo, you don't need to specify it in the config file
- stable_branch should be set to "yes" for releasing with translations from the l10n stable branch (0.x.y releases) and "no" for releasing with translations from trunk (0.x.0 releases)
- For the other fields, refer to config.ini for documentation.
$ for i in ktp-* telepathy-logger-qt; do cd $i; git tag -a -m "KDE Telepathy 0.4.0" v0.4.0; cd ..; done $ for i in ktp-* telepathy-logger-qt; do cd $i; git push origin --tags; cd ..; done
- Also, if you have done any commits in the stable branch that are not in master, at this point you should also merge the stable branch to master. The rule is that the commit with the tag should always be visible in the history of master.
$ for i in ktp-* telepathy-logger-qt; do cd $i; git checkout master; git merge kde-telepathy-0.4; cd ..; done
- You can verify that everything is merged by running git describe on master of all repos and grepping for the previous version:
$ for i in ktp-* telepathy-logger-qt; do cd $i; echo -n "$i " && git describe ; cd ..; done | grep 0.3
Create the tarballs
$ ./create_tarball.rb -n -a all -c telepathy_config.ini
Upload to ftp
mck182's handy shas generator - put all the tars in a separate folder, then do
for i in ktp-* telepathy-logger-qt*; do sha1sum $i; sha256sum $i; done