********* QUESTION ********* We decided during the meeting to : - branch head => rel_3 - synch dev_week with rel_3 - stabilize rel_3 - let head staying unstable, tumer having many ideas (full XML, XSLT...), that could be tested here.
I was wondering if it would not be better to : - synch dev_week and head - immediatly branch rel_3 when the synch is done - stabilize rel_3 for Koha 3 & let head unstable
That would let head with dev_week zebra integrated. Otherwise, i'm afraid someone (tumer ?) will have to merge dev_week with head anyway, to add zebra support
I think the idea was that we didnt want the dev_week stuff in head, as its quite different from how Tumer plans to build the API and code for 3.2 And if we merged dev_week to head then branched rel_3_0, we would then have to remove a bunch of stuff from head in the course of Tumers work. Tumer please correct me if I'm wrong Chris -- Chris Cormack Programmer 027 4500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz