[Sugar-devel] Sugar 0.101.3 (unstable)

[Peter Robinson]

>> > 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