[Koha-bugs] [Bug 7167] updatedatabase improvements

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167

--- Comment #28 from Paul Poulain <paul.poulain at biblibre.com> 2011-12-05 21:42:29 UTC ---
(In reply to comment #25)
> Comments from some (nut full) testing (no QA):
> 
> I see 3.07.01.xxx in the db revs.
> But what is 3.07.01 ? When do you reach 3.07.02 now? After you installed all 50
It's just here for testing purposes, and won't be pushed.
With this new system, the numbers don't matter. That's why I started a thread
about that in koha-devel.
We could decide to mark all DB revs 3.08.01 immediatly, or use an increasing
number, like 4, 5, 6, ...

> Listing them all is not helpful. 
Yep, I plan to add an improvement to display applied patches like this
3.07.01.001...3.07.01.015 (if we have applied all revs btw 001 and 0015)
and 3.07.01.001...3.07.01.015, 3.07.01.0017 (if we have applied all revs
between 001 and 015, and the 017)

> So this would be: 3.07.01 with 36 db revisions installed; 23 db revisions
> pending.
> Question: Do you allow someone to install dbrev 3.07.03.xxx while not all
> 3.07.02 are installed? I would say No. 
> Code should check that. Can we test it? 

I've proposed, and will provide an improvement for that, the following
behaviour:
* if DEBUG=0, then you will reach the update page from mainpage.pl until you've
made all update. So you *can't* switch an update.
* if DEBUG=1, then you won't reach the update page automatically. For
testers/testing purposes, it's a desired behaviour (improvement: today, you
have only the DEBUG=0 behaviour, which is OK)

Thus, you'll get:
* non linear updates, with almost the same behaviour as today, for productions
setups
* mandatory updates, except if you've DEBUG=1 (and in this case, you know what
you're doing)

-- 
Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.