claiming DB numbers for acquisition module
Hello, We are claiming numbers for acquisition module on the wiki page http://wiki.koha.org/doku.php?id=en:development:dbrevs However, for instance, this dev is done over the 3.0.x branch. We plan to move the dev to head in a few time, but the SAN-OP idea is to start using the new module in january, so that will be over 3.0.x But nevermind. the problem is for DB number claiming atm : we claim (& use the numbers we claim) DB numbers, but for instance, we don't commit. Do you think : - we can continue, the missing numbers will be added when we will move our job to head (at the price of head having 3.01.00.010 and LATER having 3.01.00.007 for example. But in alpha stage of 3.1, I don't think it's a problem) - we use a temporary number scheme, just for internal (BibLibre SAN-OP) use, and when we submit the stuff to HEAD, we claim & use the numbers. that would require only a few changes for us, just change the numbers in updatedatabase.pl before submitting. Writing it, I think the later is the best solution, so, unless you don't agree : - we will use it - we free the numbers we claimed (005 -> 009) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc NOUVEAU TELEPHONE : 04 91 81 35 08
Hello,
We are claiming numbers for acquisition module on the wiki page http://wiki.koha.org/doku.php?id=en:development:dbrevs
However, for instance, this dev is done over the 3.0.x branch. We plan to move the dev to head in a few time, but the SAN-OP idea is to start using the new module in january, so that will be over 3.0.x
But nevermind. the problem is for DB number claiming atm : we claim (& use the numbers we claim) DB numbers, but for instance, we don't commit.
Do you think : - we can continue, the missing numbers will be added when we will move our job to head (at the price of head having 3.01.00.010 and LATER having 3.01.00.007 for example. But in alpha stage of 3.1, I don't think it's a problem) I would consider this a problem in the 'alpha' stage of 3.1. From here on out, I don't think we have any excuses for having incomplete or buggy code in the RM's repo. If something is in an alpha state of development, IMO, it shouldn't be contributed until it has been tested and stabilized. That's not to say some stuff won't slip through that's not bug free, but just to make sure we're all on the same page and
- we use a temporary number scheme, just for internal (BibLibre SAN-OP) use, and when we submit the stuff to HEAD, we claim & use the numbers. that would require only a few changes for us, just change the numbers in updatedatabase.pl before submitting. Yes, this is probably the best way to proceed, when you've stabilized
On Fri, Sep 26, 2008 at 7:25 AM, Paul POULAIN <paul.poulain@free.fr> wrote: that code with known bugs won't be contributed. the code, and are ready to submit, it's a trivial exercise to change the version numbers,etc. My two cents. Josh
Writing it, I think the later is the best solution, so, unless you don't agree : - we will use it - we free the numbers we claimed (005 -> 009)
-- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc NOUVEAU TELEPHONE : 04 91 81 35 08 _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
-- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE CEO migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
Hi, On Fri, Sep 26, 2008 at 6:25 AM, Paul POULAIN <paul.poulain@free.fr> wrote:
- we can continue, the missing numbers will be added when we will move our job to head (at the price of head having 3.01.00.010 and LATER having 3.01.00.007 for example. But in alpha stage of 3.1, I don't think it's a problem)
It would be a problem. With our current mechanism, database schema changes must be applied in order.
- we use a temporary number scheme, just for internal (BibLibre SAN-OP) use, and when we submit the stuff to HEAD, we claim & use the numbers. that would require only a few changes for us, just change the numbers in updatedatabase.pl before submitting.
For now, I prefer that numbers be claimed closer to when patches are ready. You can use the DBrevs page on the Wiki to announce a schema change without claiming a specific number. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton@liblime.com p: 1-888-564-2457 x709 skype: gmcharlt
Galen Charlton a écrit :
For now, I prefer that numbers be claimed closer to when patches are ready.
As I said previously, writing it, I realized it was the best option.
You can use the DBrevs page on the Wiki to announce a schema change without claiming a specific number.
Very good idea. will do that -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc NOUVEAU TELEPHONE : 04 91 81 35 08
participants (3)
-
Galen Charlton -
Joshua Ferraro -
Paul POULAIN