[Koha-devel] Testing updatedatabase.pl changes

[Chris Cormack]

On 8 August 2011 20:13, Paul Poulain <paul.poulain at biblibre.com> wrote:
> Le 04/08/2011 11:36, Marcel de Rooy a écrit :
>>
>> Hi all,
>>
> Hi Marcel,
>>
>> My question is: Does anybody object to submitting this change as a
>> separate patch in order to facilitate db rev testing?  I think it is
>> an advantage to leave the version as is when you are only testing the
>> db rev.
>>
> If you look at my application as RM for 3.8, you'll see that I plan to
> set-up sandboxes with each ENH, to have easier testing. I was wondering
> how to deal with updatedatabase and the XXX.
> You've answered my question. So : I like this idea a lot !!!
>
> OTH : there is a small risk with this, that a forgotten XXX in a release
> break things a lot. How could we avoid this/limit this risk ?
>
> Just in case: I also had another idea = when setting up the sandbox, I
> could add in the staff news the result of any git command. Thus anyone
> testing the sandbox will also see what is to test on the left of the
> staff-homepage. Maybe we could also use this idea with this XXX stuff :
> if you detect a XXX during an UPDATEDATABASE, just add a news, with some
> red, saying "YIKES, i've detected a XXX during an updatedatabase. If
> you're testing a developer version, then no harm. If it's a production
> server, bug the developers, something has failed during version building !"
>
>
Or better use the tests and jenkins and never ever release with it set to XXX

There are lots of build tests already, and every push I do to master
runs them all, which means no conflict markers make it, no deprecated
code makes it in etc. I'm sure you plan to continue that process, if
so, theres no reason a release with XXX in it would ever get made

Chris