Warning, /graphics/digikam/PACKAGING is written in an unsupported language. File is not indexed.
0001 Notice to make release tarballs from GIT 0002 ---------------------------------------- 0003 0004 1/ Release announcements can be send to kde-i18n-docs if internationalized strings are frozen. 0005 The earlier is better. 0006 0007 2/ Commit last changes from source code to GIT. The code MUST compile in all cases. 0008 0009 3/ Update the release info in top level CMakeLists.txt and commit to GIT. 0010 0011 4/ Update the release info in appdata files for digiKam and Showfoto. Commit to GIT. 0012 0013 5/ Update NEWS file. If ChangeLog is a dry historical record of development, 0014 NEWS should focus on the improvements and changes, summarize everything since 0015 last major release. Look in bugzilla for closed file summaries. 0016 Commit to GIT. 0017 0018 Note: after a stable release, the NEWS file is moved from the root directory to the project sub-directory 0019 with the release IDs as file-name suffix. The NEWS file from the root directory is cleaned for the next release. 0020 0021 6/ Tag Git with the release version in this format: vX.Y.Z-suffix. 0022 Use these commands: 0023 0024 git tag -a vX.Y.Z-suffix -m "Create version X.Y.Z-suffix" 0025 git push origin vX.Y.Z-suffix 0026 0027 Where X is major version, Y minor version, and Z the patch version. 0028 The optional suffix is to indicate a non final release, as "-beta1" for ex. 0029 Look with "git tag" command for exiting tags in git. 0030 These git tags will be used to make tarball and all bundles. 0031 0032 7/ Edit the bootstrap.tarball and patch the value from TARBALL_VERSION. 0033 Run the bootstrap.tarball script to release digiKam source tarball. This will include all translations 0034 files and the documentation. The script compiles all translations files to see if nothing is broken. 0035 At the end, if all is fine, the tarball properties must be displayed. 0036 3 files are generated: 0037 0038 Source code tarball compressed as tar.xz. 0039 The archive signature is done with gpg. 0040 The SHA-256 checksums of files. 0041 0042 Note: if .sig files are not generated with GPG, you can process signature computation with the command line 0043 below. In this example, the GPG key is installed to ~/.gnupg/dkorg-gpg-pwd.txt. 0044 0045 cat ~/.gnupg/dkorg-gpg-pwd.txt | gpg --batch --yes --passphrase-fd 0 -stabv "tarball_file_to_sign" && mv "tarball_file_to_sign.asc" "tarball_file_to_sign.sig" 0046 0047 NOTE: project/scripts/signbundles.sh can batch sign all files in current directory. 0048 0049 8/ Upload tarball and signature to temporary FTP server at url 0050 0051 ftp://upload.kde.org/incoming for the final publication. 0052 0053 Create a "system admin task" to publish the files officially on download servers from this url: 0054 0055 https://phabricator.kde.org/maniphest/task/edit/form/2/ 0056 0057 Title: "New digiKam release X.Y.Z tarballs and bundles for Windows, Linux, and MacOS" 0058 0059 Description: 0060 0061 Destination: stable/digikam/X.Y.Z/ 0062 ... 0063 List of SHA-256 + file names 0064 ... 0065 0066 Note: for beta release, destination is "unstable/digikam/" 0067 0068 9/ Create bundles files with signatures for Linux, MacOS, and Windows. See README.BUNDLES for details. 0069 Use same workflow than source tarball. 0070 0071 10/ Create a release announcement page on digikam.org web site. 0072 0073 Web-site is hosted in a dedicated release repository: https://invent.kde.org/websites/digikam-org/ 0074 Website repository use a staging branch named "dev" to review changes before to post contents officially. 0075 See this README file for details: https://invent.kde.org/websites/digikam-org/blob/master/README 0076 The release announcement can use MarkDown format and are located to "news" directory. 0077 0078 Don't forget to patch default download links with new stable releases files in data/release.yml. 0079 0080 11/ Perform an official release announcement to these mailing-lists: 0081 0082 digikam-users@kde.org 0083 digikam-devel@kde.org 0084 kde-announce@kde.org 0085 0086 Title: digiKam X.Y.Z-suffix is released 0087 0088 Dear digiKam fans and users, 0089 0090 The digiKam development team is proud to release digiKam 0091 X.Y.Z-suffix. For more details, see announcement on 0092 digikam.org: 0093 0094 https://www.digikam.org/news/date-X.Y.Z-suffix_release_announcement/ 0095 0096 Best regards 0097 digiKam team 0098 0099 ---------------------------------------------------