On 9 March 2014 22:31, Gaurav Parida <gparid...@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.ben...@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@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
