Re: [Board] Roadmap and Release schedule for Plone 5.2 and 6.0

--===============3873458724155989479==
Content-Type: multipart/alternative; boundary="0000000000000d785d0582fade52"

--0000000000000d785d0582fade52
Content-Type: text/plain; charset="UTF-8"

hi people,

although it's not the role of the Board to direct the technical direction
of Plone, I do want to signal that I have serious concerns about the
proposed timeline for 5.2.
Not only as a member of the Board, which has to keep an eye out for
marketing, but also as member of the documentation team.

I think one month between having a RC1 and a final is way too short. There
is still a lot of polishing to be done, in (at least) the areas of

   - documentation
   - translations
   - real-world testing of migrations to Python3
   - development of installers that work for both Python2 and Python3
   - ... and probably more

One of the criticisms that were uttered *(not always in the nicest way, but
that's beside the point) *is that we should do better at Quality Assurance.
That is also a marketing issue.

So, while I fully support the idea of an ambitious to aggressive timeline,
and also that we should reach RC status (meaning no more new features), I
would *strongly* plead for more time, and a few RC releases. And then do a
final around, let's say, June 1.

5.2 is an important release; it has been argued that in terms of effect it
could have been a major release. Then, by all means, let's take it serious
enough so that we have satisfactory translations, documentation, marketing
messages, and a reasonably battle-tested migration experience before we
call it a Final.

Paul Roeland

*(Note: I'm only arguing urgently for a slowdown on the 5.2 release
schedule. I like the ambition on the 6.0 schedule, although also there I
think we're going to need a longer polishing time to make sure that we
release with good translations, documentation, installing instructions and
the like. In general we just need some time between feature-freeze and a
good Quality-Assured release, with ribbons and glitter around it)*

On Wed, Feb 27, 2019 at 12:39 PM Philip Bauer <[email protected]> wrote:

>
>
> Release-Schedule:
> - rc1 next week
> - final: 30.03.2019
>
>
>

--0000000000000d785d0582fade52
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>hi people, <br></div><div><br></div><div>although it&=
#39;s not the role of the Board to direct the technical direction of Plone,=
 I do want to signal that I have serious concerns about the proposed timeli=
ne for 5.2. <br></div><div>Not only as a member of the Board, which has to =
keep an eye out for marketing, but also as member of the documentation team=
. <br></div><div><br></div><div>I think one month between having a RC1 and =
a final is way too short. There is still a lot of polishing to be done, in =
(at least) the areas of</div><div><ul><li>documentation</li><li>translation=
s</li><li>real-world testing of migrations to Python3</li><li>development o=
f installers that work for both Python2 and Python3</li><li>... and probabl=
y more</li></ul><div>One of the criticisms that were uttered <i>(not always=
 in the nicest way, but that&#39;s beside the point) </i>is that we should =
do better at Quality Assurance. That is also a marketing issue. <br></div><=
div><br></div><div>So, while I fully support the idea of an ambitious to ag=
gressive timeline, and also that we should reach RC status (meaning no more=
 new features), I would <b>strongly</b> plead for more time, and a few RC r=
eleases. And then do a final around, let&#39;s say, June 1. <br></div><div>=
<br></div><div>5.2 is an important release; it has been argued that in term=
s of effect it could have been a major release. Then, by all means, let&#39=
;s take it serious enough so that we have satisfactory translations, docume=
ntation, marketing messages, and a reasonably battle-tested migration exper=
ience before we call it a Final.</div><div><br></div><div>Paul Roeland</div=
><div><br></div><div><i>(Note: I&#39;m only arguing urgently for a slowdown=
 on the 5.2 release schedule. I like the ambition on the 6.0 schedule, alth=
ough also there I think we&#39;re going to need a longer polishing time to =
make sure that we release with good translations, documentation, installing=
 instructions and the like. In general we just need some time between featu=
re-freeze and a good Quality-Assured release, with ribbons and glitter arou=
nd it)</i><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c=
lass=3D"gmail_attr">On Wed, Feb 27, 2019 at 12:39 PM Philip Bauer &lt;<a hr=
ef=3D"mailto:[email protected]">[email protected]</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
Release-Schedule:<br>
- rc1 next week<br>
- final: 30.03.2019<br>
<br>
<br>
</blockquote></div></div>

--0000000000000d785d0582fade52--


--===============3873458724155989479==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============3873458724155989479==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Plone-installers mailing list
Plone-installers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-installers

--===============3873458724155989479==--