Re: [Koha-devel] How about a different way of handling database updates

2010-02-02 Thread Frédéric DEMIANS
> As release maintainer for 3.0 I **had to*** create and arrange db > updates in a different order than master branch. Knowing wich db version > you were on 3.00.01 and not 3.01 was really important, even though its > management could have been improved. (Things that would add some tables > and ma

Re: [Koha-devel] How about a different way of handling database updates

2010-02-02 Thread Frederic Demians
> As release maintainer for 3.0 I **had to*** create and arrange db > updates in a different order than master branch. Knowing wich db version > you were on 3.00.01 and not 3.01 was really important, even though its > management could have been improved. (Things that would add some tables > and ma

[Koha-devel] Receiving serials item: customize item subfield population

2010-02-02 Thread Christopher Curry
Hello everyone. A few questions about serials: I'm working on getting the serials module working correctly (or at least limping along). When receiving a new item from within a subscription record, some data is automatically generated in the item record. The call number is applied (as defined

Re: [Koha-devel] Receiving serials item: customize item subfield population

2010-02-02 Thread Christopher Curry
I have more information concerning the missing $c problem. By examining the source of cgi-bin/koha/serials/serials-edit.pl, I found that "display:none" is being added to the style attribute of the div element that contains the $c input field. This attribute is controlled by line 276 of /usr/

Re: [Koha-devel] How about a different way of handling database updates

2010-02-02 Thread Joe Atzberger
There is one great advantage of the current approach, and that is that when a user says "we are on Koha version X", you know exactly what the database state for that should be. You know the tables, fields, constraints AND the codebase. To be clear, that means that you can *do development* specifi

Re: [Koha-devel] How about a different way of handling database updates

2010-02-02 Thread Michael Hafen
Reply inline. On Tue, 2010-02-02 at 16:50 -0500, Joe Atzberger wrote: > There is one great advantage of the current approach, and that is that > when a user says "we are on Koha version X", you know exactly what the > database state for that should be. You know the tables, fields, > constraints A

[Koha-devel] 3.2 alpha tagged in Git

2010-02-02 Thread Galen Charlton
Hi, I have tagged v3.02.00-alpha in Git, thereby kicking off the alpha period for 3.2. The corresponding DB revision is 3.01.00.111; I'll switch the DBrev to 3.02.00.000 for the beta. I will prepare a tarball tomorrow. At this point, 3.2 is feature complete and development should now be in pure