<div dir="ltr"><div>The idea is that the schedule will not include all open tasks ( as now) : every release page will include only features scheduled for that release. Doing so we can organize our work for two or more cycle. All the tasks not precisely scheduled could be inserted in a "open tasks" page, and included in the release as additional completed tasks.<br><br></div><div>On every release page we have also to insert a section for "hotfixes" with tasks planned or completed for minor releases (useful to track status of bugfixes).<br><br>The idea is that a new release is bounded to a few major changes or new features. All other little task could be inserted when they are ready.<br><br></div><div>Did I explain this clearly?<br><br></div><div>Davide<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-02-08 12:27 GMT+01:00 Gianluca Rigoletti <span dir="ltr"><<a href="mailto:gianluca.rigoletti@gmail.com" target="_blank">gianluca.rigoletti@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Good to hear this news!<div><br></div><div>One question: how do we manage the release page on meta?</div><div>Now we have some version release page that contains all the tasks tracked on phab.</div><div>Does it remain the same? We will still have a page with the tasks we are going to work </div><div>and we are going to programmatically release, right?</div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">2016-02-08 12:04 GMT+01:00 Davide Valsecchi <span dir="ltr"><<a href="mailto:valsecchi.davide94@gmail.com" target="_blank">valsecchi.davide94@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>2016-02-08 11:59 GMT+01:00 Cristian Baldi <span dir="ltr"><<a href="mailto:bld.cris.96@gmail.com" target="_blank">bld.cris.96@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><div dir="ltr"><div style="font-size:12.8px"><br>Hey Davide,</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">amazing job!</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">I really like this feature-based workflow.</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">Any idea about when we can start using this?</div></div></span></blockquote><div><br></div></span><div>I think that we can immediately start using it. The W2L_0.6 is already there and all the development could continue from master, where develop was already merged.<br> <br></div><span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><div dir="ltr"><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">Does this workflow also apply to the related projects like the various scripts we have or it is just for the Wiki part of WIkiToLearn?</div></div></span></blockquote><div><br></div></span><div>I think that maintaining the same scheme in all projects would be a good idea. We should have master and release branches also in submodules and in all project, to be able of referring them easily.<br><br></div><div>Bye<span><font color="#888888"><br><br></font></span></div><span><font color="#888888"><div>Davide <br></div></font></span><span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><div dir="ltr"><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">Good job again!</div><div style="font-size:12.8px"><br>Cristian</div></div></span><div class="gmail_extra"><br><div class="gmail_quote"><span>2016-02-07 21:19 GMT+01:00 Davide Valsecchi <span dir="ltr"><<a href="mailto:valsecchi.davide94@gmail.com" target="_blank">valsecchi.davide94@gmail.com</a>></span>:<br></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div><div><div><div>Hi all,<br><br></div>We have already spoken about the new git workflow on telegram channel. I've tried to summerize the proposals and I've written the new doc page with the new flow explained.<br><br><a href="http://meta.wikitolearn.org/Guide_for_the_development_of_WikiToLearn/Git_Workflow" target="_blank">http://meta.wikitolearn.org/Guide_for_the_development_of_WikiToLearn/Git_Workflow</a><br></div>and<br><a href="http://meta.wikitolearn.org/Guide_for_the_development_of_WikiToLearn/Development_workflow" target="_blank">http://meta.wikitolearn.org/Guide_for_the_development_of_WikiToLearn/Development_workflow</a><br><br></div>Tell me if you like it or what we can do better<br><br></div>Thank you!<span><font color="#888888"><br><br></font></span></div><span><font color="#888888">Davide<br></font></span></div>
<br></div></div><span>_______________________________________________<br>
WikiToLearn-Tech mailing list<br>
<a href="mailto:WikiToLearn-Tech@kde.org" target="_blank">WikiToLearn-Tech@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/wikitolearn-tech" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/wikitolearn-tech</a><br>
<br></span></blockquote></div><br></div>
</blockquote></span></div><br></div></div>
<br>_______________________________________________<br>
WikiToLearn-Tech mailing list<br>
<a href="mailto:WikiToLearn-Tech@kde.org" target="_blank">WikiToLearn-Tech@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/wikitolearn-tech" rel="noreferrer" target="_blank">https://mail.kde.org/mailman/listinfo/wikitolearn-tech</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div><div dir="ltr">Gianluca</div></div>
</font></span></div>
</blockquote></div><br></div>