[Koha] Koha releases - Clarification/correction

[Chris Cormack]

On 7 July 2010 19:09,  <david at lang.hm> wrote:
> On Wed, 7 Jul 2010, Chris Cormack wrote:

>> I don't think anyone is punishing the replacements for their
>> predecessors, at least I am not. What I am reacting to is the policy
>> that came out at the liblime users group meeting at ALA. Which states
>> that code will be developed in isolation by PTFS, it will then go
>> through a testing phase, and then liblime customers will get it for a
>> period of 6 months. At that point it will then be placed in a public
>> repository for the rest of the world.
>
> part of what I was responding to was in a message that I appear to have
> deleted where someone worded it as if the work to be done needed to be done
> entirely by PTFS. The point I was trying to make is that that attitude is
> also damaging (or at the very least it can significantly prolong the
> existing damage)
>
Ahh, I think the email said, "It is the developers responsibility to
send the patch in a format that can be applied" or words to that
effect. IE, the developer should rebase against the branch the patch
is to be applied to before sending the patch. Release managers have
enough work to do without having to rebase and fix conflicts that they
have to guess at the correct resolution for.

Having said that, currently the 2 people rebasing the harley code
(developed and released by ptfs, not inherited by anyone) are the 3.2
and 3.4 release managers, while dealing with patches and branches that
don't need to be rebased ...... slow going.
You can check the progress here
http://wiki.koha-community.org/wiki/PTFS_Harley_Integration
And the rebased branches are published here
http://git.koha-community.org/gitweb/?p=koha.git;a=summary

The code will eventually merged, but there's doing it the easy way,
and doing it the hard way, this is the hard way, and I see no reason
for it. Nor to have to do this all over again every 6 months.

Chris