[Sugar-devel] Sugar 0.101.3 (unstable)

[Walter Bender]

On Mon, Mar 10, 2014 at 10:42 AM, Manuel Quiñones <manuq at laptop.org> wrote:
> We recently added a Release Notes section in developer.sugarlabs.org :-)
>
> http://developer.sugarlabs.org/release-notes/102.md.html

This will be very nice for developers. Maybe less nice for our end
users. Seems we will probably need both. I'll point to this page from
the wiki page.

>
> We agreed to add the deprecations notes there.
>
> 2014-03-09 21:10 GMT-03:00 Walter Bender <walter.bender at gmail.com>:
>> It didn't take me too long to pull together
>> http://wiki.sugarlabs.org/go/0.102/Notes 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
>>
>> On Sun, Mar 9, 2014 at 8:04 PM, Daniel Narvaez <dwnarvaez at gmail.com> 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 <godiard at sugarlabs.org> 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 <dwnarvaez at gmail.com>
>>>> 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 <godiard at sugarlabs.org> 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 <dwnarvaez at gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> On 9 March 2014 22:31, Gaurav Parida <gparida94 at gmail.com> 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
>>>>>>>> <walter.bender at gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Just as a rough sketch of what pulling the commit messages would look
>>>>>>>>> like, I've set up http://wiki.sugarlabs.org/go/0.102/Notes
>>>>>>>>>
>>>>>>>>> -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
>>>>>>> Sugar-devel at lists.sugarlabs.org
>>>>>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Gonzalo Odiard
>>>>>>
>>>>>> SugarLabs - Learning Software for children
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Daniel Narvaez
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Gonzalo Odiard
>>>>
>>>> SugarLabs - Learning Software for children
>>>
>>>
>>>
>>>
>>> --
>>> Daniel Narvaez
>>
>>
>>
>> --
>> Walter Bender
>> Sugar Labs
>> http://www.sugarlabs.org
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
> --
> .. manuq ..



-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org