Flyspray - The bug killer!

  • Status Assigned
  • Percent Complete
    20%
  • Task Type Information
  • Category Installer and Upgrader
  • Assigned To
    peterdd
  • Operating System All
  • Severity Medium
  • Priority Very Low
  • 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 - 23.08.2015
Last edited by peterdd - 15.08.2016

FS#2040 - FS1.0 Release builds

  • Use github releases for the release? peterdd: Yes, currently only source releases without 3rd party vendors.

The Flyspray 1.0alpha1 .zip file release unzips directly to the current directory.

.zip files from github unzip to it’s own directory (flyspray-master.zip unzips to flyspray-master/ ). This is a bit safer, because you cannot accidently mess your directory structure with it.

  • The release should contain the binary fontawesome files instead of linking to the external CDN. Removes one dependency/singlepointoffailure. How this can be configured for automation? included in Flyspray source now. :-)
  • document how a release is exactly created. (consistency, reliability, automation, knowledge sharing for maintainers see below :-) )
  • Get in contact with os distributions, that could add Flyspray releases to their repositories (*BSD, Linux distributions, ..) This repositories could add the dependencies like ADODB within the packages (.rpm, .deb,..)
  • Get in contact with web hosting providers who provide integreated 1-click installs of software for their web hossting customers.
  • Get in contact with container builders (docker, ..)

Steps how to do a Flyspray release (since Flyspray 1.0 RC)

  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-rc1
  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 satisfied with layout
  4. Run buildscripts for different php versions (see comments at FS#2040)
  5. Upload the created .zip and .tgz files to https://github.com/Flyspray/flyspray/releases
  6. Test the created blobs on different servers too.
  7. Edit the https://github.com/Flyspray/flyspray.github.io/blob/master/_docs/download.md and link the source and packaged .zip and .tgz files
  8. 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
  9. Send an email to the Flyspray mailing list
  10. 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-rc to 1.0-rc1 if you are releasing Flyspray 1.0 RC1. Must be the exact version you set in includes/class.flyspray.php .

Maybe we can use this sequence as template on bugs.flyspray.org for releases? :-)

Project Manager
peterdd commented on 09.04.2016 16:15

This is how I build prepackaged release files at the moment for php5.4 and php5.5 on a german 1und1 managed server. (They provide several versions of PHP on the ssh command line.)

wget https://github.com/Flyspray/flyspray/archive/v1.0-rc.zip

unzip v1.0-rc.zip
cd flyspray-1.0-rc
#just for info about exact version
php5.4-cli -v
php5.4-cli -r "readfile('https://getcomposer.org/installer');" | php5.4-cli
php5.4-cli composer.phar install
rm composer.phar
rm composer.lock
cd ..
zip -r  flyspray-1.0-rc_php54.zip flyspray-1.0-rc
tar czf flyspray-1.0-rc_php54.tgz flyspray-1.0-rc
rm -rf flyspray-1.0-rc


unzip v1.0-rc.zip
cd flyspray-1.0-rc
# just for info about exact version
php5.5-cli -v
php5.5-cli -r "readfile('https://getcomposer.org/installer');" | php5.5-cli
php5.5-cli composer.phar install
rm composer.phar
rm composer.lock
cd ..
zip -r  flyspray-1.0-rc_php55.zip flyspray-1.0-rc
tar czf flyspray-1.0-rc_php55.tgz flyspray-1.0-rc
rm -rf flyspray-1.0-rc

mv v1.0-rc.zip _v1.0-rc.zip
Project Manager
peterdd commented on 09.04.2016 16:27

This is for Flyspray v1.0-rc1 (release today I hope)

On another linux hosting with php versions 5.3 and 5.6 available. (They provide also several versions of PHP on the ssh command line, but a bit different naming scheme.)

mv v1.0-rc1.zip _v1.0-rc1.zip
wget https://github.com/Flyspray/flyspray/archive/v1.0-rc1.zip

unzip -o v1.0-rc1.zip
cd flyspray-1.0-rc1
# just for info about exact version
php-5.3 -v
php-5.3 -r "readfile('https://getcomposer.org/installer');" | php-5.3
php-5.3 composer.phar install
rm composer.phar
rm composer.lock
# fix for oauth2-client v0.3 ( the last version that works with php5.3.* )
mv vendor/league/oauth2-client/src/Grant/AuthorizationCode.php vendor/league/oauth2-client/src/Grant/Authorizationcode.php
cd ..
zip -r  flyspray-1.0-rc1_php53.zip flyspray-1.0-rc1
tar czf flyspray-1.0-rc1_php53.tgz flyspray-1.0-rc1
rm -rf flyspray-1.0-rc1

unzip -o v1.0-rc1.zip
cd flyspray-1.0-rc1
# just for info about exact version
php-5.6 -v
php-5.6 -r "readfile('https://getcomposer.org/installer');" | php-5.6
php-5.6 composer.phar install
rm composer.phar
rm composer.lock
cd ..
zip -r  flyspray-1.0-rc1_php56.zip flyspray-1.0-rc1
tar czf flyspray-1.0-rc1_php56.tgz flyspray-1.0-rc1
rm -rf flyspray-1.0-rc1
Pablo Lezaeta commented on 22.08.2017 09:09

Has ben more than a year since RC1 and more than 6 months since RC4, There are plans for a RC5 or should I open a different bug for that issue?

Project Manager
peterdd commented on 24.08.2017 22:00

Yes, there should be a rc5 release soon.

Hope I can spend a day on one of the next weekends for packaging/documentation based on current github master.

Quite low activity on Flyspray development this year - I know. :-/

Project Manager
peterdd commented on 05.10.2017 00:33

Released now as v1.0-rc6 (I skipped the rc5 number for release)

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing