Releases and Patching: Difference between revisions

From OpenPetra Wiki
Jump to navigation Jump to search
 
(60 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Releases ==
== Releases ==
The deliverables are:  
The deliverables are:  
* the tar.gz files (server-debian-postgresql, server-debian-centos, client) which could be the base for manual installs, and for RPMS
* the tar.gz binary file which could be the base for manual installs, and for RPMS. see https://get.openpetra.org/latest
* the standalone installer for Windows
* the remote client installer for Windows (not published on Sourceforge, since it would be bound to an IP address)
** a special tar.gz file that is used as a base for building the patches (see below)


=== Things todo for a SourceForge release ===
=== Things todo for an Open Source release ===
==== Update translations from/to Launchpad ====
* Download the latest language files from Launchpad using <code>nant translation</code>
** Adding new languages (if desired)
*** New languages might have been downloaded after running <code>nant translation</code>. These would show up in the 'Unversioned' section of Bazaar Explorer. If we really want to add one of those new languages to OpenPetra then perform these steps:
**** Add DLL in section '<code>[Files]</code>' in file <code>setup\petra0300\standalone\standalone.iss<code>;
***** e.g. <code>Source: ..\..\..\delivery\bin\es-ES\OpenPetra.resources.dll; DestDir: {app}/bin30/es-ES</code> for Spanish
**** Add language at task '<code>downloadTranslations<code>' in file <code>i18n\i18n.build</code>;
***** e.g. <code><move file="${dir.root}/i18n/de.po" tofile="${dir.root}/i18n/de-DE.po"/></code> for German
**** Bazaar-Add the language file that is showing in the 'Unversioned' bazaar section so it is under Version Control.
* Generate the latest translation template using <code>nant buildTranslationTemplate</code>
* run <code>nant uncrustify</code> since <code>nant translation</code> reformats some of the code and the changed source code files might not conform to our uncrustify rules.
* Commit to Launchpad trunk using Bazaar.


==== Short version ====
* develop on dev branch.
* Test with Appveyor (https://ci.openpetra.org), Test mysql on LBS (https://lbs.solidcharity.com/package/solidcharity/openpetra/openpetra-test-server-mysql).
* update Release Notes in https://github.com/openpetra/openpetra/tree/dev/setup/petra0300/releasenotes; see python script get_issues.py https://gist.github.com/tpokorra/d608a8dde183e7bb51f135e052b301cc
* merge into test branch.
* update Weblate and Sync translations to/from Github: https://weblate.openpetra.org/
* build the binary tarball on lbs (https://lbs.solidcharity.com/package/solidcharity/openpetra/openpetra-bin-tarball)
* done automatically: update https://get.openpetra.org/openpetra-latest-bin.tar.gz to point to the new tarball
* install on demo.test.openpetra.org (similar to demo.openpetra.org)
* try to run /home/openpetra/openpetra-server.sh update
* build the latest demo databases: https://lbs.solidcharity.com/package/solidcharity/openpetra/demodb
* then again build the binary tarball so that the latest base.yml.gz is included, and rebuild openpetranow-mysql-test
* download the latest demo database to the demo.openpetra.org container
* try restore demo database from command line. try running month end. try a report. try to edit partner
* install on demo.openpetra.org
* merge to master, and prod
* Github: tag the release, set the milestone date, close the milestone
* post release notes on the forum and on the github release, link on twitter/facebook, fediverse, and on OpenPetra Download Blog
* build prod openpetranow package
* install on hosted OpenPetra.com. test with my instance: "www.openpetra.com test Zugang"


==== Mantis Tracker ====
==== What can/should be done a day or even a few days before the actual release date====
===== Ensuring that all fixed Bugs have set "Fixed in Version" =====
Performing all the steps that are listed here on this page can take - on average - a day if the last release has been some months ago. However, the time it takes on the day of the release can potentially be reduced by doing several steps a day or even a few days in advance.
We need to make sure that every developer has set "Fixed in Version" on all the bugs that have 'Closed' or 'Resolved' state. As this is normally forgotten on quite a few bugs, it must be done manually before a release in order to have a complete list of bugs that were fixed in this release.


* Using Mantis,
These are the steps that can be done before the actual release:
** filter for all bugs with 'closed' and 'resolved' state that have 'Fixed in Version' equals 'none', 'Resolution' equals 'fixed' and 'Hide Status' equals 'None'.
===== Testing the release packages before the release =====
** do the same for 'resolved' state on a new Tab of your web browser.
* create a branch called test in https://github.com/tpokorra/openpetra
** In both steps, make a note of all bug numbers that have been 'closed'/'resolved' since the date of the last release.
* increase the version in db/version.txt to 2016.07.0-0
* Run the MantisUpdateVersions Tool
* build the test branch of the packages:
** The tool resides in <code>\setup\tools\MantisUpdateVersions</code. As it isn't get built by <code>nant generateSolution</code> you need to load the C# Project 'MantisUpdateVersions.csproj' into your favourite IDE and compile it.
** https://lbs.solidcharity.com/package/solidcharity/openpetra/openpetra-bin-tarball
** Open a command shell and change the directory to <code>'\setup\tools\MantisUpdateVersions\obj\x86\Debug'</code>
** https://lbs.solidcharity.com/package/solidcharity/openpetra/openpetranow-mysql-test
** Execute the following command: <code>MantisUpdateVersions.exe -sf-username:pokorra -sf-pwd:xyz -bug-id:abc,def,ghi -version-fixed-in:"Alpha 0.2.20"</code>, replacing the value for <code>-sf-username</code> and <code>-sf-pwd</code> with your SourceForge username and password, the string that follows after '-version-fixed-in:' with the current release number and <code>abc,def,ghi</code> with the 1..n Mantis Bug ID's that you found in the two Mantis filter steps.
*** ''NOTE'': The SourceForge user that is specified in this command needs to have 'administrator' privileges in the Mantis Bugtracker so that the commands that are issued by this program can succeed!


===== Creating Static 'Bugs Resolved in this Release' HTML File =====
* [[Manual tests before a release]]
We need to create a static HTML page that contains the list of all bugs that got resolved/closed in this release. This page gets uploaded to SourceForge and is linked to from the Release Notes and News Updates.
* Simply filtering Mantis and creating a permalink [using the 'Create Permalink' functionality on the search result page] does not work with Mantis in the version that is used on Sourceforge!
* Instead, do the following:
** In FireFox (Chrome is bad with external links),
*** go to https://sourceforge.net/apps/mantisbt/openpetraorg/view_all_bug_page.php,
*** create the follwing Filter:
**** fixed in version 0.0.2.0 [use current release number],
**** hide none (thus the list will includes resolved and closed bugs)
** Click on Print, and store the file in some local directory
* Upload that file to eg. <code>[http://openpetraorg.sourceforge.net/ReleaseDetails/BugsFixed_Alpha-0.2.8.htm http://openpetraorg.sourceforge.net/ReleaseDetails/BugsFixed_Alpha-0.2.8.htm]</code> [use current release number] using some FTP program (directory <code>username/openpetraorg@web.sourceforge.net:/home/project-web/openpetraorg/htdocs/ReleaseDetails</code>).


===== Preparing the text for the [[Releases and Patching#Release Notes|Release Notes]]=====
* Usually this can be done once the testing phase begins which precedes the release - that might even be a week before the release because even if there is still a major new functionality that might get added before the release will be done this will be known by now and can be written up already.
** Obviously the text needs to be looked at carefully at the day of the release, but most of time-consuming work will have been done by then.
=====Preparing up-to-date screenshots=====
* Check which (if any) screenshots on the 'Screenshots' page of the OpenPetra website need updating.
* If any need updating and these screens won't change any more until the release is done, take those screenshots now and store them until the day of the release has come as this process takes some time.
** If any screenshot is to be replaced check the file name of the existing screenshot and name the new one accordingly.
** Screenshots are listed on that page in a smaller size, and when one clicks on them the full size is shown. The smaller size can also already be prepared in advance.
==== Update translations from/to Weblate ====
* Download the latest language files from Weblate. Do a synchronization, and that might create a pull request.


==== Release Notes ====
==== Release Notes ====
Line 58: Line 61:


====DB Patches====
====DB Patches====
* add new patch sql file to db/patches
* add new patch .cs and .sql file to https://github.com/openpetra/openpetra/tree/master/csharp/ICT/Petra/Server/lib/MSysMan/DBUpgrades
** this only applies to increased patch numbers, not builds! so the patch sql file will always be for version.release.patch-0, where 0 is the build number.
** file with new version number needs to exist even if there were no DB changes!
*** in that case it is best to simply copy an existing file that also contained no DB changes.
* modify file <code>version.txt</code> in directory db/patches so it contains the Version Number of the OpenPetra release that you are creating.
* modify file <code>version.txt</code> in directory db/patches so it contains the Version Number of the OpenPetra release that you are creating.
** Alternative: use the commandline argument <code>-D:ReleaseID=0.0.2.0</code> [use current release number] to specify the build number when running <code>nant buildWindowsStandalone</code> in step [[Releases and Patching#Installers | Installers]].


====Final Steps====
====Final Steps====
===== Bazaar =====
===== Building the release =====
* Tag trunk with the name of the new release (e.g. <code>ALPHA-0.2.22</code> [use current release number])
* increase the version in db/version.txt
 
* merge branch into master, and into test and prod branches
===== Installers =====
* rebuild the package in LBS
* On a Windows machine:
** https://lbs.solidcharity.com/package/solidcharity/openpetra/openpetranow-mysql-test
** Perform a <code>bzr update</code> on your check-out of Bazaar trunk
* create a tag and a release in https://github.com/openpetra/openpetra
** Run <code>nant buildWindowsStandalone -D:ReleaseID=0.0.2.0</code> [use current release number]
** Perform a <code>bzr revert</code> to get rid of i18n files that are not wanted.
 
* On a linux machine (on openpetrabuild: /home/timop/bzr):
** Perform a <code>bzr update</code> on your check-out of Bazaar trunk
** Run <code>nant buildLinuxSourceforgeRelease -D:ReleaseID=0.0.2.0</code> [use current release number]. 
** Perform a <code>bzr revert</code> to get rid of i18n files that are not wanted.
 
* Installers end up in the <code>/delivery/</code> directory.
* Test installers on Windows and Linux.
* Upload all installers to SourceForge using some FTP program: <code>username@frs.sourceforge.net:/home/pfs/project/o/op/openpetraorg/openpetraorg</code>


===== Making the Release Known to the Public =====
===== Making the Release Known to the Public =====
====== Website ======
====== Website ======
* Screenshots
** see [[Releases and Patching#Preparing_up-to-date_screenshots|above]] for the preparation of up-to-date screenshots
** update the 'Screenshots' page of the website (English, German).
* Release Notes
* Release Notes
** Post Release Notes on the 'Download' page of the website (English, German).
** Post Release Notes on the 'Download' page of the website (English, German).
Line 105: Line 95:
*** Content of the emails: exactly the same as in the tweets - except if there is a News Update that corresponds with the release: in this case the content of what got posted in the 'News' section of the website.
*** Content of the emails: exactly the same as in the tweets - except if there is a News Update that corresponds with the release: in this case the content of what got posted in the 'News' section of the website.


===== Mantis Tracker =====
== Patches ==
* Next Release needs to be added to all projects
** as this is tedious if done manually use the tool <code>MantisUpdateVersions.exe -sf-username:pokorra -sf-pwd:*** -release-version:0.0.2.0</code> from <code>/setup/tools/</code> for that [use current release number]


=== patching the database ===
OP_CUSTOMER=op_dev /home/openpetra/openpetra-server.sh upgradedb


== Patches ==
=== Testing the server upgrade ===
* we use the bsdiff algorithm from http://www.daemonology.net/bsdiff/ for binary diffs and patching
on a testing machine: test.openpetra.org
* see more about the [[patchtool]]
* Install the previous version on a clean container:
curl https://get.openpetra.org | bash -s old
* run the upgrade:
/home/openpetra/openpetra-server.sh update
* Test the login on https://test.openpetra.org
 
=== Reverting to previous version ===
export OLDVERSION="2020.04.0-3"
export TagDemoDB="UsedForNUnitTests-202004"
export OP_CUSTOMER=op_demo
yum remove openpetranow-mysql-test
yum install openpetranow-mysql-test-$OLDVERSION.x86_64 --enablerepo=lbs-solidcharity-openpetra
MYSQL_CMD="drop database $OP_CUSTOMER" /home/openpetra/openpetra-server.sh mysql
/home/openpetra/openpetra-server.sh initdb
demodbfile=/tmp/demoWith1ledger.yml.gz
curl --silent --location https://github.com/openpetra/demo-databases/raw/$TagDemoDB/demoWith1ledger.yml.gz > $demodbfile
/home/openpetra/openpetra-server.sh loadYmlGz $demodbfile


=== patching the database ===
Now update:
Standalone:
yum clean expire-cache --disablerepo="*" --enablerepo="lbs-solidcharity-openpetra"
* standalone is always delivered with SQLite database
/home/openpetra/openpetra-server.sh update
* we don't have patch installers yet. a full installer will update the program files, and add sql files for patching the database (setup\petra0300\standalone\patches). We cannot write to the user's directory, since the installer must be run as admin.
* on the next startup of OpenPetra Standalone by the user, csharp\ICT\Petra\Server\app\Main\ServerManager.cs EstablishDBConnection() will check for the database version, and UpdateSQLiteDatabase() will update the sqlite database
* this will also run "UPDATE s_system_defaults SET s_default_value_c = '{0}' WHERE s_default_code_c = 'CurrentDatabaseVersion';"

Latest revision as of 04:25, 27 October 2021

Releases

The deliverables are:

Things todo for an Open Source release

Short version

What can/should be done a day or even a few days before the actual release date

Performing all the steps that are listed here on this page can take - on average - a day if the last release has been some months ago. However, the time it takes on the day of the release can potentially be reduced by doing several steps a day or even a few days in advance.

These are the steps that can be done before the actual release:

Testing the release packages before the release
Preparing the text for the Release Notes
  • Usually this can be done once the testing phase begins which precedes the release - that might even be a week before the release because even if there is still a major new functionality that might get added before the release will be done this will be known by now and can be written up already.
    • Obviously the text needs to be looked at carefully at the day of the release, but most of time-consuming work will have been done by then.
Preparing up-to-date screenshots
  • Check which (if any) screenshots on the 'Screenshots' page of the OpenPetra website need updating.
  • If any need updating and these screens won't change any more until the release is done, take those screenshots now and store them until the day of the release has come as this process takes some time.
    • If any screenshot is to be replaced check the file name of the existing screenshot and name the new one accordingly.
    • Screenshots are listed on that page in a smaller size, and when one clicks on them the full size is shown. The smaller size can also already be prepared in advance.

Update translations from/to Weblate

  • Download the latest language files from Weblate. Do a synchronization, and that might create a pull request.

Release Notes

  • Update Release notes files in setup/petra0300/releasenotes. (English: releasenotes.html, German: releasenotes_de.html)
    • Format:
      • never empty the contents of that file as it is meant to be cumulative!
      • rather, add the Release Notes that pertain to the current release on top of the file.
      • follow the format of the previous Release Notes.
  • Commit the changed files to Launchpad trunk using Bazaar.


DB Patches

Final Steps

Building the release
Making the Release Known to the Public
Website
  • Screenshots
    • see above for the preparation of up-to-date screenshots
    • update the 'Screenshots' page of the website (English, German).
  • Release Notes
    • Post Release Notes on the 'Download' page of the website (English, German).
      • Format of the Release Notes: refer to previous posts.
      • Include download link for the Windows Installer and the Linux packages that pertain to this release.
      • Include link to the static HTML file that contains the list of closed bugs that pertains to this release (created in an earlier step in these instructions).
  • News Update
    • If there is a News Update that corresponds with the release (which often is the case): post news update in the 'News' section of the website (English, German).
      • Format of the News Update: refer to previous posts.
      • Include link to the 'Download' page of the website (English, German).
Notifications
  • Send out a 'Tweet' on Twitter
    • Tweet about the release on twitter (English [user: openpetraorg], German [user: openpetraorgde])
    • Format of the Tweet: refer to previous tweets that pertain to releases.
  • Mailing Lists
    • Send out information on mailing lists (English, German).
      • Content of the emails: exactly the same as in the tweets - except if there is a News Update that corresponds with the release: in this case the content of what got posted in the 'News' section of the website.

Patches

patching the database

OP_CUSTOMER=op_dev /home/openpetra/openpetra-server.sh upgradedb

Testing the server upgrade

on a testing machine: test.openpetra.org

  • Install the previous version on a clean container:
curl https://get.openpetra.org | bash -s old
  • run the upgrade:
/home/openpetra/openpetra-server.sh update

Reverting to previous version

export OLDVERSION="2020.04.0-3"
export TagDemoDB="UsedForNUnitTests-202004"
export OP_CUSTOMER=op_demo
yum remove openpetranow-mysql-test
yum install openpetranow-mysql-test-$OLDVERSION.x86_64 --enablerepo=lbs-solidcharity-openpetra
MYSQL_CMD="drop database $OP_CUSTOMER" /home/openpetra/openpetra-server.sh mysql
/home/openpetra/openpetra-server.sh initdb
demodbfile=/tmp/demoWith1ledger.yml.gz
curl --silent --location https://github.com/openpetra/demo-databases/raw/$TagDemoDB/demoWith1ledger.yml.gz > $demodbfile
/home/openpetra/openpetra-server.sh loadYmlGz $demodbfile

Now update: 

yum clean expire-cache --disablerepo="*" --enablerepo="lbs-solidcharity-openpetra"
/home/openpetra/openpetra-server.sh update
Retrieved from ‘https://wiki.openpetra.org/index.php?title=Releases_and_Patching&oldid=4887’