<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>The branching of docs.xfce.org into a 4.14 namespace has been
completed.</p>
<p>Please let me know if you see any issues.</p>
<p>Thanks,</p>
<p>Kevin<br>
</p>
<div class="moz-cite-prefix">On 8/14/19 9:29 PM, Kevin Bowen wrote:<br>
</div>
<blockquote type="cite"
cite="mid:22e069dc-3140-d8d6-1514-45cc0682d8f5@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>I can pick up branching the 4.14 docs as I did with the 4.12
docs. I've already got the images locally and the list of pages
that need to be built.<br>
</p>
<p>Kevin<br>
</p>
<div class="moz-cite-prefix">On 8/14/19 7:54 AM, Simon Steinbeiss
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAApLaz3S4Vb-CL4fG43PdA4=D8jvhdqpiokZPzzNsck9VSRM4w@mail.gmail.com">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<div dir="ltr">
<div>Hi everyone,</div>
<div><br>
</div>
<div>this message is mostly directed towards our core devs,
but I thought it may still be relevant for everyone to read.</div>
<div><br>
</div>
<div>As we managed to stick to our deadline for the final
release (mostly :)) it's time to collect the open points
from 4.14 and the first steps toward 4.16.</div>
<div>Please help - especially with completing the 4.14 steps,
so we can start for 4.16 with a clean slate soonish!<br>
</div>
<div><br>
</div>
<div>=== 4.14 post steps ===<br>
</div>
<div>* Create the tour (website)</div>
<div>* Finish updating the slider with new screenshots on the
frontage</div>
<div>* Add more screenshots to the screenshots page</div>
<div>* Create xfce-4.14 branches for each core component</div>
<div>* Only push bugfixes to the 4.14 branches and new
features into the master branch</div>
<div>* 4.14 patch releases shall happen on the 4.14 branches
obviously<br>
</div>
<div>* Consider transifex sync for 4.14 branch and possibly
deactivating 4.10 and 4.12 (whatever may still be active)</div>
<div>* Consider branching the docs straight away into a 4.14
namespace (same as we did for 4.12) so we can anytime update
the master pages during the 4.16 cycle<br>
</div>
<div><br>
</div>
<div>=== 4.16 kickoff ===<br>
</div>
<div>* Start to think about the roadmap and fill things in
here: <a
href="https://wiki.xfce.org/releng/4.16/roadmap#roadmapplanned_features"
moz-do-not-send="true">https://wiki.xfce.org/releng/4.16/roadmap#roadmapplanned_features</a></div>
<div>* Consider making this a short/er cycle again, so maybe
just a few features and some further cleanups (also, don't
forget we want to migrate to Gitlab next)<br>
</div>
<div><br>
</div>
<div>I hope that makes sense to you all. The most important
bit is certainly about creating the branches and not pushing
new features into 4.14. (What is bugfix and what is feature
is a bit relative and obviously up to your own judgement.)<br>
</div>
<div><br>
</div>
<div>Cheers</div>
<div>Simon<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Xfce4-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Xfce4-dev@xfce.org" moz-do-not-send="true">Xfce4-dev@xfce.org</a>
<a class="moz-txt-link-freetext" href="https://mail.xfce.org/mailman/listinfo/xfce4-dev" moz-do-not-send="true">https://mail.xfce.org/mailman/listinfo/xfce4-dev</a></pre>
</blockquote>
</blockquote>
</body>
</html>