<div dir="ltr">The discussion started because Peter would like to have release notes for unstable releases. (Though he might be content with those being just the git logs).<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On 10 March 2014 01:01, Gonzalo Odiard <span dir="ltr"><<a href="mailto:godiard@sugarlabs.org" target="_blank">godiard@sugarlabs.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I am not thinking in doing it for every unstable release, just for 0.102.<div>I already did it for 0.100, I can volunteer to do it again in 0.102</div><span class="HOEnZb"><font color="#888888"><div><br></div>
<div>Gonzalo</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">On Sun, Mar 9, 2014 at 8:58 PM, Daniel Narvaez <span dir="ltr"><<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">The thing is, I don't have time to do that manually for each unstable release. We either need a volunteer to do it or a way to generate it automatically from the log (which was the goal of my suggestion).<br>
<div><div class="gmail_extra"><div><div><br><div class="gmail_quote">On 10 March 2014 00:56, Gonzalo Odiard <span dir="ltr"><<a href="mailto:godiard@sugarlabs.org" target="_blank">godiard@sugarlabs.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">In the end, we need a summary to the end public, we can prepare it like in the past,<div>based in the commit messages.</div><div><br></div><div>Gonzalo</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
<div><div>
On Sun, Mar 9, 2014 at 8:41 PM, Daniel Narvaez <span dir="ltr"><<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>></span> wrote:<br></div></div><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>On 9 March 2014 22:31, Gaurav Parida <span dir="ltr"><<a href="mailto:gparida94@gmail.com" target="_blank">gparida94@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>Keeping the commit messages, will help in knowing the changes done in a release. The documentation aspect of a new release will be easily handled. <br></div>+1 for the idea.<br><div class="gmail_extra">
<div>
<div class="gmail_quote"><br>On Mon, Mar 10, 2014 at 2:35 AM, Walter Bender <span dir="ltr"><<a href="mailto:walter.bender@gmail.com" target="_blank">walter.bender@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Just as a rough sketch of what pulling the commit messages would look<br>
like, I've set up <a href="http://wiki.sugarlabs.org/go/0.102/Notes" target="_blank">http://wiki.sugarlabs.org/go/0.102/Notes</a><br>
<span><font color="#888888"><br>
-walter<br>
</font></span><div><div><br></div></div></blockquote></div></div>The mockups look good. It would be great if each one them also has the link to the merge request.<br><br></div><div class="gmail_extra">
In my opinion, the commit messages will be more understandable, if we put some guidelines for them.<br></div><div class="gmail_extra">like preappend the commit messages with with [Feature] / [Bug Fix #xxxx] / [Defect] / [Upgrade] from now on... <br>
</div></div>
</blockquote></div><br></div></div></div><div class="gmail_extra">We could include in the release notes only the subject of commits tagged like that. That would avoid to have too many irrelevant implementation details in the notes and also to simply omit commits that are not relevant (like refactorings etc).<br>
</div></div>
<br></div></div><div>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br></div></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Gonzalo Odiard<br><br><div>SugarLabs - Learning Software for children<br></div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><br></div></div><span><font color="#888888">-- <br>Daniel Narvaez<br>
</font></span></div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Gonzalo Odiard<br><br><div>SugarLabs - Learning Software for children<br></div></div>
</div>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Daniel Narvaez<br>
</div>