http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167 --- Comment #76 from Paul Poulain <paul.poulain@biblibre.com> --- (In reply to comment #75)
QA Comment: Jonathan: I am very sorry, but I fear that you missed my main point somehow from comment70 /comment71 about the distinction between numbered and unnumbered dbrevs. Please reread. Just in short: In user mode installer should run the numbered dbrevs; the update form only lists both dbrevs for reference. There is no need to run dbrevs from there in that mode. In dev mode installer still runs the numbered dbrevs, the update form allows you to run the other ones in any order. question : if you're in user mode, it means you're running a published version right ? So there should not be any unnumbered dbrev ? conclusion = isn't the current behaviour correct ?
Secondly, see my comment on Mainpage AND Authorization. Please move the extended version check back from mainpage to checkauth but later in time (only for new sessions). Note also that the double login problem still remains. After applying your patch, and installing the new cpan module, I had to login twice again. (See the cookie comment?) I won't object as long as it does not require checking on *every* page.
See also my earlier comment on Stable version. This needs some additional precaution, since we will not implement it in master and 3.8.X at the same time. (The version compare in 3.8.X will be different from master.) When upgrading to 3.10, you cannot completely prevent running some dbrevs for a second time. (But some could be skipped when comparing your checksums between 3.8 and 3.9 folder.) This issue will reappear at every new version (e.g. comparing checksums again between 3.10 and 3.11 folder, etc.) Couldn't we also decide that 3.8 DBrevs are made on the old updatedatabase.pl, DBrevs for 3.10 are in the new one ? So no need to backport this enhancement to 3.8.
-- You are receiving this mail because: You are watching all bug changes.