Hello world, OK, i'll release 2.2.9 soon, based on rel_2_2_7 branch+some bugs ported from rel_2_2 (and only bugfixes) I've reviewed more than 100 commits on rel_2_2 branch, and am sure the stability of this branch is not that good enough to have a 2.2.9 release based on rel_2_2. On the other hand, 3-4 major bugfixes have been done, a release is needed. So i'll do it. But I want to speak of the next step. In the last weeks, we had : - HEAD : a lot of activity from hdl & me : code cleaning mainly. it should now be done. - dev_week : a lot of activity from ccfls (kyle & cindy) and some from libLime as well : some features backported from head (holidays) and a new feature ClubsAndServices, for some testing - rel_2_2 : a lot of activity from libLime : backported some features from head (holidays), and some new features (item level reserves, serials routing lists I think it is important that all commiters says what they are doing & when they think they will get enough stability to have a roadmap and a timeline. I also think it's important that all features added on 2.2 / dev_week were also added on head (or we could loose the features. That can be acceptable, but at least we will be aware of the fact, to avoid any bad surprise) Last but not least : I think we should speak of our organisation : it seems that rel_2_2 branch will become a new version with new features. I strongly think we should not call this version 2.2.10, but 2.4 or something like that, to point that it has new features & probably less stability. So we will need a 2.4RM. In the last 3 weeks, I could not get in touch with Joshua, or almost. I'm happy that business is going well for libLime, but, pls, try to find time to the community, we need everybody to work in the same direction, and know the direction we are going ;-) Our (hdl & me) position is clear : - I support 2.2.x branch as Release Maintainer - We work hard on head to achieve a 3.0 stable asap. code cleaning is done (although it's never done in fact. But all what had to be done is done), we plan to work on YUI asap, to have koha 3.0 stable for early Q3 Waiting for everybody thoughts, wishes & args ;-) -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
Hi all, Paul POULAIN wrote:
- dev_week : a lot of activity from ccfls (kyle & cindy) and some from libLime as well : some features backported from head (holidays) and a new feature ClubsAndServices, for some testing
We'll definitely port the features that ccfls has added to dev_week to head, but I can't say exactly when. Right now we're focused on migrating to dev_week; our official migration date for our first library is May 21. Right now we're not doing any work with head. Maybe it's time for another IRC meeting? cheers, c. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Cindy Murdock Network Administrator Meadville Public Library | CCFLS http://meadvillelibrary.org | http://ccfls.org
On 28/04/2007, at 1:29 AM, Paul POULAIN wrote:
Hello world,
OK, i'll release 2.2.9 soon, based on rel_2_2_7 branch+some bugs ported from rel_2_2 (and only bugfixes)
I've reviewed more than 100 commits on rel_2_2 branch, and am sure the stability of this branch is not that good enough to have a 2.2.9 release based on rel_2_2. On the other hand, 3-4 major bugfixes have been done, a release is needed. So i'll do it.
But I want to speak of the next step. In the last weeks, we had : - HEAD : a lot of activity from hdl & me : code cleaning mainly. it should now be done. - dev_week : a lot of activity from ccfls (kyle & cindy) and some from libLime as well : some features backported from head (holidays) and a new feature ClubsAndServices, for some testing - rel_2_2 : a lot of activity from libLime : backported some features from head (holidays), and some new features (item level reserves, serials routing lists
I can speak for some of the rel_2_2 commits. Serials routing lists was there already, albeit broken for libraries that have 1 biblio - 1 biblioitem - many items. All of the commits around serials have been to do with fixing bugs. Including the serial routing ones, the only way to fix it, was with item level reserves. The way this has been added is that nothing changes at all, unless you explicity switch item level reserves on. I tried to do it in the least disruptive way possible, so that nothing at all changes. Holidays was also partially backported already, all the commits in the last 2 weeks have been tidying that up. So from our end we are trying to work towards stable working features. AFAIK we plan to add no new features to rel_2_2 all the commits were around getting the existing features working properly. Hope this helps Chris -- Chris Cormack chris.cormack@liblime.com VP Research and Development www.liblime.com LibLime +64 21 542 131
participants (3)
-
Chris Cormack -
Cindy Murdock -
Paul POULAIN