On 4. Apr. 2017 at 15:27, Pål Grønås Drange wrote:
Why can't every module simply make a release 2017-04 that is
frozen from April 11, and then you can simply pick that one,
and we can go on doing development as usual in the master
branch?
On 4. Apr. 2017 at 16:55, Andreas Lauser wrote:
Hi Pål,
On Dienstag, 4. April 2017 13:27:49 CEST you wrote:
> > Cut-off date for code changes: Tuesday April 11, 2017. The master branches
> > of all modules will be closed for non-trivial, non-regression and non-
> > documentation merges after this, i.e., I'll be a jerk and personally
> > revert
> Cut-off date for code changes: Tuesday April 11, 2017. The master branches of
> all modules will be closed for non-trivial, non-regression and non-
> documentation merges after this, i.e., I'll be a jerk and personally revert
> any merged code changes that do not fix serious problems thereafter.
