Hi Galen, I was wondering where we are going with 3.2 integration : - i've submitted 79 patches for new_acq some months ago. What's the status of those patches ? We have made some/many improvements, that have not be submitted anywhere yet (it's on our local repo). I would be very happy to submit them, but don't know where to put them yet. - the other features are on http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=shortlog;h=biblibre-integrat... There are a lot of patches all around, and I was wondering how/when they are supposed to reach 3.2 repository. I think delaying too much integration of patches results in slowing the release. BibLibre faces a lot of added work to deal with multiple repository (we have one for new_acq, one for other features -sponsored by Aix-Marseille Universities-, one for 3.0.x, ...). And, more important probably, the community suffers from not knowing exactly what has been done and how. I think what we should do now is : integrate all our (BibLibre) patches into the 3.2 repo as soon as possible, open widely the repo, and let everyone play with it ("Release Soon, Release Often"). I'm sure other developers from Chris C. to PTFS, Tamil, PTFS-Europe, ByWaterSolutions,... will be very happy to test & play with all those patches. If some other people have "finished" or "almost finished" features, they should be added as well. It's not a matter of putting BibLibre 1st, it's just a matter of being agile ! cheers -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
Hi Paul, On Mon, Aug 31, 2009 at 12:16 PM, paul POULAIN<paul.poulain@biblibre.com> wrote:
I was wondering where we are going with 3.2 integration : - i've submitted 79 patches for new_acq some months ago. What's the status of those patches ? We have made some/many improvements, that have not be submitted anywhere yet (it's on our local repo). I would be very happy to submit them, but don't know where to put them yet.
Along with the patches from other submitters, I'm working to parcel them onto topic branches. Once feature-freeze is completed on the sixth, the following day I'll be publishing all topic branches and starting work to consolidate them into master - the main task will be serializing the database changes. Once that's done, it will mean that September will mean a lot of work from all of us to digest the new features and submit bugfixes. Regards, Galen -- Galen Charlton gmcharlt@gmail.com
2009/9/1 Galen Charlton <gmcharlt@gmail.com>:
Hi Paul,
On Mon, Aug 31, 2009 at 12:16 PM, paul POULAIN<paul.poulain@biblibre.com> wrote:
I was wondering where we are going with 3.2 integration : - i've submitted 79 patches for new_acq some months ago. What's the status of those patches ? We have made some/many improvements, that have not be submitted anywhere yet (it's on our local repo). I would be very happy to submit them, but don't know where to put them yet.
Along with the patches from other submitters, I'm working to parcel them onto topic branches. Once feature-freeze is completed on the sixth, the following day I'll be publishing all topic branches and starting work to consolidate them into master - the main task will be serializing the database changes.
Excellent plan.
Once that's done, it will mean that September will mean a lot of work from all of us to digest the new features and submit bugfixes.
Yep it's going to be a busy month alright. But I do think thats the best way to do it. Having the major changes or topic branches is really the only managable way to bring the code in. Chris
participants (3)
-
Chris Cormack -
Galen Charlton -
paul POULAIN