[Koha-devel] Koha 3.8 release schedule & perltidy process

Paul Poulain paul.poulain at biblibre.com
Thu Mar 8 15:22:19 CET 2012


Le 08/03/2012 14:36, Marcel de Rooy a écrit :
> Hi Paul,
Hi Marcel,

> What is the exact procedure?
> All patches submitted before March 23 or signed-off before March 23
are candidates for the 3.8 release?
> If so, how do we separate them easily from the patches submitted
later? What is strong feature freeze exactly here?
By "included" I mean "pushed to master". I don't mean "submitted" or
"signed-off".
A major feature that is submitted on march 22nd, signed-off on march 24
won't be in 3.8, it will be delayed to the next release.

[well, if something really cool is QAed on march 24 I may decide to
delay the feature freeze by a day. I'll check bugzilla in the days
before the string freeze and encourage ppl to sign-off/QA. Fortunatly,
the european hackfest take place this week, so we will have many ppl
available to test anything cool ;-) ]

After the 1st "feature freeze" I will still accept small enhancements.
that's why we can call it "soft FF".

After the "strong feature freeze" NO enhancements at all will be added,
to let translator and testers enough time to do their work.

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


More information about the Koha-devel mailing list