[Koha-devel] Release Manager 3.6

[Chris Nighswonger]

On Wed, May 11, 2011 at 2:24 PM, Galen Charlton <gmcharlt at gmail.com> wrote:

> Hi,
>
> On Wed, May 11, 2011 at 1:01 PM, Chris Cormack <chris at bigballofwax.co.nz>
> wrote:
> > 1/ Continue with the current workflow, patches signed off, passed qa,
> > then into master, with the goal to increase the rate patches are
> > signed off
>
> +1
>
>
+1 as well.


> > As Paul has noted in another thread, I am not comfortable with
> > allowing patches into master untested, and I don't think I could do a
> > good job as RM if that were to become the case. In that case I would
> > rather become one of the developers submitting patches again, so
> > perhaps 3 and 4 are the same for me.
>
> This would be a huge step backwards.
>

It would indeed. The 3.4-plus workflow and release schedules have been
changes necessary to the substructure of Koha in order for it to support the
rapidly expanding superstructure. Reverse them, and the entire thing is in
danger of collapsing.

Anyone who expects their work to be pushed untested is out of line imho.

Kudos to Chris C for a job well done and sticking to the rules.

Kind Regards,
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110511/0f585af8/attachment.htm>