[koha-commits] main Koha release repository branch new/bug_6700 created. v3.06.00-270-gbb92ac1

[Git repo owner]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "main Koha release repository".

The branch, new/bug_6700 has been created
        at  bb92ac1ee01a9b781ca2a7adab4beec28e6edeaa (commit)

- Log -----------------------------------------------------------------
commit bb92ac1ee01a9b781ca2a7adab4beec28e6edeaa
Author: Chris Cormack <chris at bigballofwax.co.nz>
Date:   Mon Aug 8 23:45:00 2011 +0200

    Test to check for XXX in kohaversion.pl or updatedatabase.pl
    
    Signed-off-by: Marcel de Rooy <m.de.rooy at rijksmuseum.nl>
    Works as advertised.
    
    Signed-off-by: Marcel de Rooy <m.de.rooy at rijksmuseum.nl>
    Amended the original patch of Chris to add two exceptions for a line in SetVersion and TransferToNum.
    
    http://bugs.koha-community.org/show_bug.cgi?id=6700
    Signed-off-by: Paul Poulain <paul.poulain at biblibre.com>

commit c8982e1ab41ef54ba66afd3ed313e81cde307004
Author: Marcel de Rooy <m.de.rooy at rijksmuseum.nl>
Date:   Thu Jun 30 09:34:23 2011 +0200

    6700: Better handling of version numbers in updatedatabase
    
    Contains a few lines of code for updatedatabase routines SetVersion and TransformToNum in order to facilitate testing new db revisions which are still marked XXX.
    Currently, the XXX as added in a proposed patch generates an error in the version compare. Additionally, running SetVersion while testing the upgrade is annoying and not needed. In testing stage you would like to keep your version number as is. The version number should of course be incremented when the patch is pushed. A simple test accomplishes that.
    
    Signed-off-by: Julian Maurice <julian.maurice at biblibre.com>

-----------------------------------------------------------------------


hooks/post-receive
-- 
main Koha release repository