That will be great!If you can automate the insertion of the values of these tags to the current upcoming release notes post (like the automated comments in the issue tracker) at submit, that will be helpful for everyone. (Of course, reverts should also be noted) And then, finally, the poster will just remove the redundant entries (that were reverted), if any and post them. I would also add a hook for every Dev branching (that will include the WebKit\V8\Chrome revision), since it is usually a good thing to have in the release notes and it is not always included. Plus, the release notes will be more consistent and accurate this way.
☆PhistucK On Fri, Jul 17, 2009 at 20: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? > > - a > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
