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

sven <[email protected]> Fri, 01 Mar 2019 06:31:39 +0100
Newsgroups gmane.comp.web.zope.plone.installers,gmane.comp.web.zope.plone.teams.framework
Message-ID <[email protected]>
--===============2934388819212016684==
Content-Type: multipart/alternative; boundary="=-SaejAGGeZvuq6cylwzGN"


--=-SaejAGGeZvuq6cylwzGN
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

Hi !
Same here, well said !
I am only talking here about the documentation part, the current state
of the docs for 5.2 and 6 is far away from publishing.
Also, since we are on it, I would like to ask where I can find docs of
Plone 6, like the new UI, etc.
We started to rewrite and rebuild the whole docs from scratch, so far
this is working well and the quality, readability, etc improved a lot.
But since we have no idea what of the current docs will stay and which
parts will be different we just have some basic covered, yet.
Please let us know (Open an issue) about docs of Plone 6.
The same goes with with things like bobtemplates, will they worl with
Plone 6, should we adjust or remove them from the 'core' docs ?
Thanks !
On Thu, 2019-02-28 at 22:20 +0100, Paul Roeland wrote:
> 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
> documentationtranslationsreal-world testing of migrations to
> Python3development of installers that work for both Python2 and
> Python3... and probably moreOne 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
> > 
> > 
> > 
> > 
> > 
> 
> _______________________________________________Plone-installers
> mailing listPlone-installers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/plone-installers

--=-SaejAGGeZvuq6cylwzGN
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr"><head></head><body style=3D"text-align:left; direction:lt=
r;"><div>Hi !</div><div><br></div><div>Same here, well said !</div><div><br=
></div><div>I am only talking here about the documentation part, the curren=
t state of the docs for 5.2 and 6 is far away from publishing.</div><div><b=
r></div><div>Also, since we are on it, I would like to ask where I can find=
 docs of Plone 6, like the new UI, etc.</div><div><br></div><div>We started=
 to rewrite and rebuild the whole docs from scratch, so far this is working=
 well and the quality, readability, etc improved a lot.</div><div><br></div=
><div>But since we have no idea what of the current docs will stay and whic=
h parts will be different we just have some basic covered, yet.</div><div><=
br></div><div>Please let us know (Open an issue) about docs of Plone 6.</di=
v><div><br></div><div>The same goes with with things like bobtemplates, wil=
l they worl with Plone 6, should we adjust or remove them from the 'core' d=
ocs ?</div><div><br></div><div>Thanks !</div><div><br></div><div>On Thu, 20=
19-02-28 at 22:20 +0100, Paul Roeland wrote:</div><blockquote type=3D"cite"=
 style=3D"margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex=
"><div dir=3D"ltr"><div>hi people, <br></div><div><br></div><div>although i=
t'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. <br></div><div>Not only as a member of the Board, which has to ke=
ep 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 (a=
t least) the areas of</div><div><ul><li>documentation</li><li>translations<=
/li><li>real-world testing of migrations to Python3</li><li>development of =
installers that work for both Python2 and Python3</li><li>... and probably =
more</li></ul><div>One of the criticisms that were uttered <i>(not always i=
n the nicest way, but that's beside the point) </i>is that we should do bet=
ter at Quality Assurance. That is also a marketing issue. <br></div><div><b=
r></div><div>So, while I fully support the idea of an ambitious to aggressi=
ve timeline, and also that we should reach RC status (meaning no more new f=
eatures), I would <b>strongly</b> plead for more time, and a few RC release=
s. And then do a final around, let's say, June 1. <br></div><div><br></div>=
<div>5.2 is an important release; it has been argued that in terms of effec=
t it could have been a major release. Then, by all means, let's take it ser=
ious enough so that we have satisfactory translations, documentation, marke=
ting messages, and a reasonably battle-tested migration experience before w=
e call it a Final.</div><div><br></div><div>Paul Roeland</div><div><br></di=
v><div><i>(Note: I'm only arguing urgently for a slowdown on the 5.2 releas=
e 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 rele=
ase with good translations, documentation, installing instructions and the =
like. In general we just need some time between feature-freeze and a good Q=
uality-Assured release, with ribbons and glitter around it)</i><br></div></=
div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On=
 Wed, Feb 27, 2019 at 12:39 PM Philip Bauer &lt;<a href=3D"mailto:bauer@sta=
rzel.de">[email protected]</a>&gt; wrote:<br></div><blockquote type=3D"cite"=
 style=3D"margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex=
"><br>
<br>
Release-Schedule:<br>
- rc1 next week<br>
- final: 30.03.2019<br>
<br>
<br>
</blockquote></div></div>
<pre>_______________________________________________</pre><pre>Plone-instal=
lers mailing list</pre><a href=3D"mailto:Plone-installers-5NWGOfrQmneRv+LV9MX5urNAH6kLmebB@public.gmane.org=
.net"><pre>Plone-installers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org</pre></a><pre><br></pre><=
a href=3D"https://lists.sourceforge.net/lists/listinfo/plone-installers"><p=
re>https://lists.sourceforge.net/lists/listinfo/plone-installers</pre></a><=
pre><br></pre></blockquote></body></html>

--=-SaejAGGeZvuq6cylwzGN--



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


--===============2934388819212016684==
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

--===============2934388819212016684==--