Jump to content

MakingTarballs: Difference between revisions

From KDE Community Wiki
Halla (talk | contribs)
No edit summary
Halla (talk | contribs)
 
(2 intermediate revisions by the same user not shown)
Line 16: Line 16:
  git clone kde:kde-dev-scripts
  git clone kde:kde-dev-scripts


Update the information in the config.ini file to reflect the right tag and version number, and run the script
Go into the createtarball folder, update the information in the config.ini file to reflect the right tag and version number, commit and push and run the script


  ./create_tarball_kf5.rb -n -a krita
  PATH/TO/kde-dev-scripts/createtarball/create_tarball_kf5.rb -n -a krita
 
Releases also should be announced on  [email protected].
 
The tarball can be signed:
 
gpg --output krita-3.1.2.0.tar.gz.sig --detach-sign krita-3.1.2.0.tar.gz

Latest revision as of 12:45, 27 January 2017

Making a Source Tarball

Make sure:

  • That the version is set correctly in the toplevel CMakeLists.txt
  • That the version of the krita.xmlgui file has been bumped up
  • That there is a tag set for the release like this:
 git tag -a v3.0.99.89 -m "Krita 3.0.1 Alpha" e278ff7
 git push origin --tags

Then:

Check out kde-dev-scripts

git clone kde:kde-dev-scripts

Go into the createtarball folder, update the information in the config.ini file to reflect the right tag and version number, commit and push and run the script

PATH/TO/kde-dev-scripts/createtarball/create_tarball_kf5.rb -n -a krita

Releases also should be announced on [email protected].

The tarball can be signed:

gpg --output krita-3.1.2.0.tar.gz.sig --detach-sign krita-3.1.2.0.tar.gz