<div dir="ltr">Great! So I'll let you know when 0.101.4 is tagged. </div><div class="gmail_extra"> <div class="gmail_quote">On 10 March 2014 01:10, Walter Bender <<a href="mailto:walter.bender@gmail.com" target="_blank">walter.bender@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It didn't take me too long to pull together <a href="http://wiki.sugarlabs.org/go/0.102/Notes" target="_blank">http://wiki.sugarlabs.org/go/0.102/Notes</a> and I am happy to do the same again for the other unstable releases. We need to do some more work for the stable release as per Gonzalo's comments. -walter <div class="HOEnZb"><div class="h5"> On Sun, Mar 9, 2014 at 8:04 PM, Daniel Narvaez <<a href="mailto:dwnarvaez@gmail.com">dwnarvaez@gmail.com</a>> wrote: > 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). > > > On 10 March 2014 01:01, Gonzalo Odiard <<a href="mailto:godiard@sugarlabs.org">godiard@sugarlabs.org</a>> wrote: >> >> I am not thinking in doing it for every unstable release, just for 0.102. >> I already did it for 0.100, I can volunteer to do it again in 0.102 >> >> Gonzalo >> >> >> On Sun, Mar 9, 2014 at 8:58 PM, Daniel Narvaez <<a href="mailto:dwnarvaez@gmail.com">dwnarvaez@gmail.com</a>> >> wrote: >>> >>> 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). >>> >>> On 10 March 2014 00:56, Gonzalo Odiard <<a href="mailto:godiard@sugarlabs.org">godiard@sugarlabs.org</a>> wrote: >>>> >>>> In the end, we need a summary to the end public, we can prepare it like >>>> in the past, >>>> based in the commit messages. >>>> >>>> Gonzalo >>>> >>>> >>>> On Sun, Mar 9, 2014 at 8:41 PM, Daniel Narvaez <<a href="mailto:dwnarvaez@gmail.com">dwnarvaez@gmail.com</a>> >>>> wrote: >>>>> >>>>> On 9 March 2014 22:31, Gaurav Parida <<a href="mailto:gparida94@gmail.com">gparida94@gmail.com</a>> wrote: >>>>>> >>>>>> 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. >>>>>> +1 for the idea. >>>>>> >>>>>> On Mon, Mar 10, 2014 at 2:35 AM, Walter Bender >>>>>> <<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a>> wrote: >>>>>>> >>>>>>> Just as a rough sketch of what pulling the commit messages would look >>>>>>> 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> >>>>>>> >>>>>>> -walter >>>>>>> >>>>>> The mockups look good. It would be great if each one them also has the >>>>>> link to the merge request. >>>>>> >>>>>> In my opinion, the commit messages will be more understandable, if we >>>>>> put some guidelines for them. >>>>>> like preappend the commit messages with with [Feature] / [Bug Fix >>>>>> #xxxx] / [Defect] / [Upgrade] from now on... >>>>> >>>>> >>>>> 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). >>>>> >>>>> _______________________________________________ >>>>> Sugar-devel mailing list >>>>> <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> >>>>> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> >>>>> >>>> >>>> >>>> >>>> -- >>>> Gonzalo Odiard >>>> >>>> SugarLabs - Learning Software for children >>> >>> >>> >>> >>> -- >>> Daniel Narvaez >> >> >> >> >> -- >> Gonzalo Odiard >> >> SugarLabs - Learning Software for children > > > > > -- > Daniel Narvaez </div></div><div class="HOEnZb"><div class="h5">-- Walter Bender Sugar Labs <a href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a> </div></div></blockquote></div> -- Daniel Narvaez </div>