[Sugar-devel] Sugar 0.101.3 (unstable)

Gaurav Parida gparida94 at gmail.com
Sun Mar 9 17:31:19 EDT 2014


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...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20140310/9e5793fd/attachment.html>


More information about the Sugar-devel mailing list