Re: Freezing for 2.18

[Werner LEMBERG]

> Last time around, we released 2.17.0 in the _wake_ of releasing
> 2.16.0, and only _then_ the extensive skyline patches were placed
> into 2.17 and 2.17.1 was released with them.  That worked reasonably
> well.  We don't have the resources for parallel development and
> testing, and it does not even appear that we have the release
> mechanisms.

+1

As said before, it's probably best if all developers actually use the
`stable' code since noone likes to switch between branches (due to the
enormous compilation hurdles).  This means that there is a code freeze
in the `master' branch for a certain time.

Emacs does the same, ditto the Linux kernel, so there are many
precedents.


    Werner