Now that we have a new framework team it is time to start planning the
3.1 release. 3.1 is intended to be a low-risk upgrade which can follow
the 3.0 release quickly. The release cycle has to be short so we can
get things out to people. Here is my proposal:

- all proposed updates for have to be submitted by christmas
- framework team finishes reviewing by january 9
- accepted changes are merged in the days after that
- first pre-release for 3.1 happens on january 15
- final release for 3.1 happens first half of february

In order to make reviewing simple all updates have to be submitted in
the form of a working buildout. And to keep the 3.1 process smooth they
have to include all migrations, finished user interfaces and
documentation. We will not do any polishing after merging - that has to
be done beforehand.

Judging by the current activity I expect there to be only 2 or 3
proposals in a mergeable state. That is not much, so you should be able
to enjoy some christmas vacation as well :)


Wichert Akkerman <[EMAIL PROTECTED]>    It is simple to make things.                   It is hard to make things simple.

Framework-Team mailing list

Reply via email to