Releases and Patching: Difference between revisions

From OpenPetra Wiki
Jump to navigation Jump to search
Line 1: Line 1:
== Releases ==
== Releases ==
To build a release, check <code>nant help</code> for the current syntax of <code>nant buildRelease</code>.
The deliverables are:  
The deliverables are:  
* the tar.gz file which could be the base for manual installs, and for RPMS
* 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 file is also used as a base for building the patches (see below)
* the standalone installer for Windows
* the standalone installer for Windows
* the remote client 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 a SourceForge release ===
Line 20: Line 18:
* add new patch sql file to db/patches
* add new patch sql file to db/patches
* Tag bzr
* Tag bzr
* On a windows machine: run nant buildRelease -D:ReleaseID=0.0.2.0
 
* On a linux machine: run nant buildRelease -D:ReleaseID=0.0.2.0. bzr update, bzr revert. (on openpetrabuild: /home/timop/bzr)
* On a windows machine: run <code>nant buildWindowsStandalone -D:ReleaseID=0.0.2.0</code>
* On a linux machine: run <code>nant buildLinuxSourceforgeRelease -D:ReleaseID=0.0.2.0</code>. bzr update, bzr revert. (on openpetrabuild: /home/timop/bzr)
* test installer on Windows and Linux
* test installer on Windows and Linux



Revision as of 13:23, 29 September 2011

Releases

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 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

  • On a windows machine: run nant buildWindowsStandalone -D:ReleaseID=0.0.2.0
  • On a linux machine: run nant buildLinuxSourceforgeRelease -D:ReleaseID=0.0.2.0. bzr update, bzr revert. (on openpetrabuild: /home/timop/bzr)
  • test installer on Windows and Linux
  • Upload to SF: username@frs.sourceforge.net:/home/pfs/project/o/op/openpetraorg/openpetraorg
    • link the release notes
  • Post Release Notes on website, twitter
  • Update Mantis Tracker:
    • add next release to all projects

Patches

patching the database

Standalone:

  • standalone is always delivered with SQLite database
  • 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';"