On Fri, Jul 17, 2009 at 10:48, Aaron Boodman <[email protected]> wrote:
> > I propose we add a new tag to changelist descriptions: > > RELEASE_NOTE=<description of something interesting that users would > like to know happened in this build> > > It would be up to the developer to decide whether something was worth > going in the release notes. > > In the extension world, the reason I specifically want this is I want > to keep people testing the system up to date with changes. I have been > trying to do this with a mail I send to chromium-extensions@ with each > new release, but it is hard to stay in sync with build schedule. > > Thoughts? I've been thinking of something along the same lines. I was also considering a ReleaseNotes file, like a ChangeLog but only to announce noteworthy changes. The advantages are that it can be edited post-commit and that your notes get reverted if your change gets reverted. In any case, if you want to pioneer 'add an optional RELEASE_NOTES line to your log description', I'm all for it. > > > - a > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
