Prepare 3.0.0 source Kexi 3/KDb/KProperty/KReport releases
Closed, ResolvedPublic

Description

3.0.0 Final:

  • Decide on a release date
  • 2016-10-05
  • Create 3.x git branches and push if needed
  • On release day run tarme with the correct origin and version
  • Verify the tarball and do a test build, possibly ask peers to build on their systems as well.
  • Upload .xz and .sig to ftp://depot.kde.org/.
  • File a ticket (e.g. stable:T3944, unstable:T3801) with sha256sum for the sysadmins to move the tarballs to http://download.kde.org.
  • Create and push tags (or run tagme to tag your release in git)
  • Once the sysadmins have processed your ticket announce the release in whatever way that seems reasonable (blog post, kde-announce-apps@kde.org, twitter, facebook, g+ etc. etc. etc.)

Prepare alpha/beta releases, get to know the scripts:

  • Decide on a release date
  • 2016-09-19
  • Decide on a string freeze time frame before the release. This freeze should be upwards of 7 days before a release. For most medium sized projects a freeze of 14 days is recommendable.
  • 2016-09-13
  • When string freeze draws closer make sure the correct branches are set for i18n trunk or i18n stable (depending on what you want to release). If you change the settings also make sure to inform the translators of the move either on IRC or by mail at kde-i18n-doc@kde.org
  • Inform the translation teams kde-i18n-doc@kde.org when you start string freeze and tell them when the release is due so they can plan accordingly.
  • On release day run tarme with the correct origin and version
  • Verify the tarball and do a test build, possibly ask peers to build on their systems as well.
  • Upload to ftp://depot.kde.org/ and note the README in there.
  • File a ticket with the sysadmins to move your tarball into a suitable place on http://download.kde.org. If you are unsure about where to put it you can ask the release-team@kde.org for some guidance.
  • Create and push tags (or run tagme to tag your release in git)
  • Once the sysadmins have processed your ticket announce the release in whatever way that seems reasonable (blog post, dot.kde.org, kde-announce-apps@kde.org, twitter, facebook, g+ etc. etc. etc.)

Some chat about what's available:

<jstaniek>   hi, looking for a volunteer who would manage release scripts for repos (kexi, kdb, 
kproperty, kreport), there are no scripts no tarballs with source/translations; until there's a 
workforce releases would only happen on GIT
<tosky>  jstaniek: just to understand, do you want to write another set of release script?
<jstaniek>   tosky: I'd like to outsource 99% of that :)
<jstaniek>   especially i18n
<jstaniek>   are release scripts created by forking some existing ones? (these days)
<tosky>  kde-dev-scripts, createtarball/create_tarball_kf5.rb
<jstaniek>   yep.. kf5 scripts look as the closest fit 
<boud>   jstaniek: that one worked out of the box for krita
<jstaniek>   very good
<jstaniek>   -- trying to push the betas out close to Akademy
<Riddell>    jstaniek: kde:releaseme is your friend
<Riddell>    jstaniek: one simple command to make all your tars
<tosky>  Riddell: I think it has some issues with translated documentation
<Riddell>    always works for me
<tosky>  Riddell: can you check the last changes in create_tarball_kf5? It was changed to 
properly use ki18n_install and kdoctools_install, maybe you can apply them to releaseme
<tosky>  Riddell: it didn't work,  I think I told you some time ago, translation of khelpcenter 
documentation was not properly placed when khelpcenter was part of Plasma
<tosky>  boud: ehm, about that, at leat in the last krita-3.0.99.91.tar.gz one of the po is 
missing (kritacrashhandler.po), I think you may want to add it to the config.ini file for 
create_tarball_kf5
<jstaniek>   honestly I was trying to find official recommendation docs and found mostly 
https://community.kde.org/Policies/Application_Lifecycle 
https://community.kde.org/Release_Team/Release_Process
<jstaniek>   I know many projects have own scripts and I'd like to avoid this
<Riddell>    jstaniek: I don't think there are any official recommended ways to do it, as 
plasma release dude I recommend releaseme
<jstaniek>   Riddell: very good, thanks; as there is 2 weeks of time recommended for the 
release process I think I'd be announcing availability of a preview version on GIT, blogging, 
get opinions and try the scripts
<Riddell>    jstaniek: for plasma I make beta tars 2 weeks before which is a test incase the 
tars are broken in some way or I've missed something out, that's also the time I make the 
stable branches (which is also done by releaseme)
staniek created this task.Sep 3 2016, 10:58 PM
staniek renamed this task from Propere release to Prepare release.
staniek renamed this task from Prepare release to Prepare first source release.
staniek renamed this task from Prepare first source release to Prepare first source Kexi 3 release.
staniek updated the task description. (Show Details)Sep 5 2016, 12:43 PM
staniek renamed this task from Prepare first source Kexi 3 release to Prepare first source Kexi 3/KDb/KProperty/KReport releases.
staniek updated the task description. (Show Details)Sep 5 2016, 12:45 PM
staniek updated the task description. (Show Details)Sep 12 2016, 11:33 PM
staniek updated the task description. (Show Details)Sep 20 2016, 11:27 AM
staniek moved this task from TODO 3.2 to Backlog on the KEXI board.Sep 29 2016, 11:12 PM
staniek updated the task description. (Show Details)Sep 30 2016, 4:07 PM
staniek updated the task description. (Show Details)
staniek renamed this task from Prepare first source Kexi 3/KDb/KProperty/KReport releases to Prepare 3.0.0 source Kexi 3/KDb/KProperty/KReport releases.Oct 3 2016, 9:59 AM
staniek updated the task description. (Show Details)
staniek moved this task from Backlog to TODO 3.2 on the KEXI board.
staniek updated the task description. (Show Details)Oct 4 2016, 9:17 PM
staniek updated the task description. (Show Details)
staniek updated the task description. (Show Details)Oct 5 2016, 6:32 PM
staniek updated the task description. (Show Details)Oct 10 2016, 11:09 PM
staniek closed this task as Resolved.