The commit messages for our changes to Sugar core tend to be pretty decent. If we grab those and put them into a wiki page, then we could manually edit them into something more friendly to read once per release cycle. I volunteer to do the editing.
Catching changes to the core activities is a bit more haphazard. But once the page is set up, we can put a call out to the maintainers in Fructose (a relatively small group). -walter On Sun, Mar 9, 2014 at 3:33 PM, Peter Robinson <pbrobin...@gmail.com> wrote: >>> > this release marks our feature freeze for 0.102. Now let's focus on bug >>> > fixing! >>> >>> It would be useful to see release notes for each release so as to know >>> what's changed, added and needs to be tested rather than a tarball >>> list dumped to the list. >> >> >> I agree, but at the moment I have no time to do that myself. We could have a >> page in sugar-docs and reviewers would fill in items that are release note >> worthy when pushing pull requests. Sort of worried about raising the review >> barrier though. What do people think about that? > > Why can't it be auto generated using git and then you just have to > make sure there's decent commit messages. Ultimately I think good > commit messages should be compulsory because it tells you why changes > were made. > > Peter > _______________________________________________ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel