Flyspray - The bug killer!

  • Status Closed
  • Percent Complete
    80%
  • Task Type TODO
  • Category Backend/Core
  • Assigned To
    peterdd
  • Operating System All
  • Severity High
  • Priority High
  • Reported Version 1.0-rc
  • Due in Version 1.0
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray - The bug killer!
Opened by peterdd - 15.08.2016
Last edited by peterdd - 08.12.2016

FS#2195 - Release Flyspray 1.0-rc2/rc3/rc4

  1. Edit includes/class.flyspray.php on github.com and set the correct version for the release there (remove the ' dev’ from the version string), commit as new branch e.g. 1.0-rc2
  2. Prepare a new release on https://github.com/Flyspray/flyspray/releases , write a summary of changes since last release, choose the branch you created in the previous step, save as “draft”.
  3. “Release” the Flyspray source on github when satified with layout
  1. Run buildscripts for different php versions (see comments at FS#2040)
  2. Upload the created .zip and .tgz files to https://github.com/Flyspray/flyspray/releases
  3. Edit the https://github.com/Flyspray/flyspray.github.io/blob/master/_docs/download.md and link the source and packaged .zip and .tgz files
  4. Write a new article with a summary of highlights of changes since last release for the www.flyspray.org frontpage on https://github.com/Flyspray/flyspray.github.io/tree/master/_posts/News
  5. Important: If all is nice and shiny: Update the version string on www.flyspray.org https://github.com/Flyspray/flyspray.github.io/blob/master/version.txt so admins of flyspray get informed a new Flyspray release is available now. For instance change from 1.0-rc1 to 1.0-rc4 if you are releasing Flyspray 1.0-rc4. Must be the exact version you set in includes/class.flyspray.php .
Closed by  peterdd
08.12.2016 00:12
Reason for closing:  Complete

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing