On Thu, 11 May 2006 03:03:17 +0100, Hanno Schlichting
[EMAIL PROTECTED] wrote:
Hi again.
From what I have read so far, we tend into the direction of giving this
release a bit more time. So here is an updated roadmap proposal. The one
thing it tries to be is realistic about the dates if we
Hanno Schlichting wrote:
[..]
Plone 3.0
-
June 26, plip freeze (no more plip's are accepted)
August 21, proposal freeze (review bundles must be ready)
September 25, feature freeze (all features have been merged)
October 22, first beta release
December 18, first release candidate
January
Raphael Ritz wrote:
First, I think we should really encourage the SoC projects by
defining a time line and process that offers the **possibility**
of getting results from SoC projects into the 3.0 release.
My intention here was to give all the SoC projects a clear statement
that their code
I think those are good points, and I certainly agree with the merits
of having that separation be clear. I just wonder whether we truly
*can* have such a separation, and whether there then is a vacuum in
leadership and policy guidance that we need to fill, because I think
people are
Maybe moving to a pattern like this (peer-review) would also make
sense for us???
/digression
Just my 0.02 Euro
Raphael
i think that is essentially what we have. in the end, the release
manager decides. the FWT is just a gatekeeper to make those decisions
manageable.
-w
--
| david
/me dons grumpy old former FWT member hat
remember, all that SoC stuff has to have bundles and be approved by you
guys. No implementing proposals after the fact. That's about the only
standing rule for this team. So if you are looking at this sort of
schedule, likely almost none of the SoC
