Re: [Framework-Team] Re: Plone 3.5

[Wichert Akkerman]

Previously Andreas Zeidler wrote:

> Andreas Zeidler wrote:
> >Hanno Schlichting wrote:
> >>The general idea that seems to have met some consensus is to go for a
> >>Plone 3.5 release up next.
> >
> >sounds good to me, +1.
>
> actually, i think it should still be plone 4.0 (with the remaining
> features deferred to 5.0 or later).  otherwise i think it's a good idea
> in the sense of "release early, release often".

+1

In hindsight I feel it was a mistake to assign a version number to Plone
trunk. It might end up being Plone 5, 6, 7 or 3000. Using Plone 4
instead of 3.5 means that we will not break  our promise to never break
stability in the 3.x, something I feel quite strongly about.

Wichert.

--
Wichert Akkerman <[hidden email]>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Plone-docs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-docs

[Kamon Ayeva-3]

Hello,

On Tue, May 5, 2009 at 3:37 PM, Wichert Akkerman <[hidden email]> wrote:

Previously Andreas Zeidler wrote:
> Andreas Zeidler wrote:

> >Hanno Schlichting wrote:
> >>The general idea that seems to have met some consensus is to go for a
> >>Plone 3.5 release up next.
> >

> >sounds good to me, +1.
>
> actually, i think it should still be plone 4.0 (with the remaining
> features deferred to 5.0 or later).  otherwise i think it's a good idea
> in the sense of "release early, release often".

+1

In hindsight I feel it was a mistake to assign a version number to Plone
trunk. It might end up being Plone 5, 6, 7 or 3000. Using Plone 4
instead of 3.5 means that we will not break  our promise to never break
stability in the 3.x, something I feel quite strongly about.

I'm +1 to allow us to progress and I agree with Wichert. That release could just be "4" with needed architectural changes some of us are waiting for such as WSGI, the next Zope 2.x, Chameleon, fixing the skin layer/resources story, a "Plone Base" distribution, and what not.

I'm -1 to introduce this as a 3.x increment because there is a highy risk that it will have a negative impact for people's perception, and make documenters, book authors, and traines life harder. It is already hard today, and the perception of our stuff being complex and difficult to follow is really the priority in what we need to fix.

My 2 eurocents.

-- Kamon


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Plone-docs mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-docs