Krita/Release/Checklist Krita Release Checklist: Difference between revisions

From KDE Community Wiki
(Created page with "= Release Checklist = Krita releases follow [http://semver.org/ semantic versioning], more or less. == Major Release == A major release is an increase of the major or minor...")
 
No edit summary
Line 2: Line 2:


Krita releases follow [http://semver.org/ semantic versioning], more or less.
Krita releases follow [http://semver.org/ semantic versioning], more or less.
== Platforms ==
* Windows: x86, x64 (boud)
* OSX: x64 (boud)
* Linux:
** Ubuntu (Dmitry)
** OpenSUSE (Leinir)
** CentOS (Boud)


== Major Release ==
== Major Release ==


A major release is an increase of the major or minor version number: 2.9 to 3.0 or 3.0 to 3.1. A major release contains a large chunk of functionality and happens about once a year, just before the yearly fundraising campaign.
A major release is an increase of the major or minor version number: 2.9 to 3.0 or 3.0 to 3.1. A major release contains a large chunk of functionality and happens about once a year, just before the yearly fundraising campaign, which means a March release.


=== Checklist ===
=== Checklist ===
Line 13: Line 22:
* Two months before
* Two months before
** Send out the booklet to journalists
** Send out the booklet to journalists
* One month
** Give the translation teams a heads-up
** Prepare the release announcement
* Just before the release
* Just before the release
** Add the new version to Bugzilla, disable the previous version. On releasing 3.0, 2.9 is no longer supported and should be disabled.
** Add the new version to Bugzilla, disable the previous version. On releasing 3.0, 2.9 is no longer supported and should be disabled.
** Create the translations tarball to integrate in the binary builds
** Update the krita.rc version number
** Add a tag to git
** Change the version number (CMakeLists.txt)
** Create the release branch
* After the release
** Update the version number  (CMakeLists.txt)
** Change to the new splash when avaialable


== Minor Release ==
== Minor Release ==
Line 22: Line 45:
=== Checklist ===
=== Checklist ===


* Two weeks
** Feature freeze
* One week
** String freeze
** Prepare the release announcement
** Give the translation teams a heads-up
* Just before the release:
* Just before the release:
** Create the translations tarball to integrate in the binary builds
** Add the new version to Bugzilla version
** Add the new version to Bugzilla version
** Update the krita.rc version number
** Add a tag to git
** Change the version number  (CMakeLists.txt)
* After the release

Revision as of 12:57, 7 December 2015

Release Checklist

Krita releases follow semantic versioning, more or less.

Platforms

  • Windows: x86, x64 (boud)
  • OSX: x64 (boud)
  • Linux:
    • Ubuntu (Dmitry)
    • OpenSUSE (Leinir)
    • CentOS (Boud)

Major Release

A major release is an increase of the major or minor version number: 2.9 to 3.0 or 3.0 to 3.1. A major release contains a large chunk of functionality and happens about once a year, just before the yearly fundraising campaign, which means a March release.

Checklist

  • Three months before
    • Start preparing the release booklet
  • Two months before
    • Send out the booklet to journalists
  • One month
    • Give the translation teams a heads-up
    • Prepare the release announcement
  • Just before the release
    • Add the new version to Bugzilla, disable the previous version. On releasing 3.0, 2.9 is no longer supported and should be disabled.
    • Create the translations tarball to integrate in the binary builds
    • Update the krita.rc version number
    • Add a tag to git
    • Change the version number (CMakeLists.txt)
    • Create the release branch
  • After the release
    • Update the version number (CMakeLists.txt)
    • Change to the new splash when avaialable


Minor Release

A minor release is an increase of the patch-level number: 2.9.1 to 2.9.2. A minor release can contain not just bug fixes but also new features. A minor release happens once every month.

Checklist

  • Two weeks
    • Feature freeze
  • One week
    • String freeze
    • Prepare the release announcement
    • Give the translation teams a heads-up
  • Just before the release:
    • Create the translations tarball to integrate in the binary builds
    • Add the new version to Bugzilla version
    • Update the krita.rc version number
    • Add a tag to git
    • Change the version number (CMakeLists.txt)
  • After the release