Archive:Release Checklist: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
No edit summary
>DonJ
Line 20: Line 20:
* Update any necessary changelogs, readmes, known_bugs
* Update any necessary changelogs, readmes, known_bugs
* Update XBMC Credits
* Update XBMC Credits
See below the version bump updates undertaken for Frodo Beta 1:
* [https://github.com/xbmc/xbmc/commit/0ac2abc2171e290f643a6b5b2ba783ab43f8d823 XBMC Version bump]
* [https://github.com/xbmc/xbmc/commit/d9c5aad1b8d2fab670eacee286b39263f898eed5 json bump]
* [https://github.com/xbmc/xbmc/commit/fc6558ad7c82538179a89faceecbaaa6a6b872be default webinterface bump]
* [https://github.com/xbmc/xbmc/pull/1781 Repo bump]


==Release==
==Release==

Revision as of 13:19, 14 November 2012

Since we don't release all that often or consistently, we seem to forget some key steps in the process. Hence, a checklist!
On this page the term "release" refers to the final stable release tag and binaries.

Testing

The following apply for all supported platforms and architectures.

  • Compile.
  • Video playback of popular codecs. (xvid, h264, vc1, mpeg2)
  • Audio playback of popular codecs. (mp3, aac(+), ogg, flac, , ac3, dts)
  • Playback from popular sources. (local, dvd, smb, http)
  • Scripts/plugins.
  • Initialization of new settings and databases.
  • Updating of settings and databases from the last stable release.

Pre-tag/branch

  • Update version string:
  • configure.in (see AC_INIT)
  • tools/android/depends/configure.in (see AC_INIT)
  • xbmc/utils/GUIInfoManager.h
  • tools/darwin/packaging/xbmc-ios/mkdeb-xbmc-ios.sh
  • tools/darwin/packaging/xbmc-atv2/mkdeb-xbmc-atv2.sh
  • xbmc/osx/Info.plist (there are two strings to change)
  • xbmc/win32/XBMC_PC.rc
  • Update any necessary changelogs, readmes, known_bugs
  • Update XBMC Credits

See below the version bump updates undertaken for Frodo Beta 1:

Release

  • scp binaries to sourceforge in staging folder. xbmc-x.yy-zz.*
  • svn export tag and scp to sourceforge. Downloading the tarball from sourceforge tag WILL NOT WORK as it doesn't keep file attributes.
  • move from staging to final location (using shell service)
  • update links and analytics on xbmc.org/download
  • add xbmc.org frontpage news item. tick 'Announcements' category also (for sidebar)
  • Add trac version and set as default milestone.
  • [WIN32] copy the file XBMC.pdb for the released binary to the team ftp server and name it accordingly (is this all we need for reading crash dumps?)

Post-release

  • Update version string in xbmc/utils/GUIInfoManager.h to pre-[NextVersion].
  • Remove blanked strings from strings.xml to liberate them for reuse.