On Wed, Jul 22, 2009 at 2:57 PM, Mark Larson (Google)<[email protected]> wrote: > On Wed, Jul 22, 2009 at 14:02, Peter Kasting <[email protected]> wrote: >> On Wed, Jul 22, 2009 at 1:49 PM, Jeremy Orlow <[email protected]> wrote: >>> >>> Here comes the bike shedding >> >> Yes, Evan already concluded that was where we were. >>> >>> RELEASE_NOTES= >> >> I thought the conclusion was that people should just write better commit >> messages? > > I still want a RELEASE_NOTES flag, but not a "NOTES=I'm repeating what I > just wrote up above." > Writing concise summaries as the first line of a description is good form > that we should encourage for all changes, not just noteworthy changes. Given > a token that says "hey, this is noteworthy or a user visible change", we can > write scripts to pull out the first line of the description for inclusion in > the release notes.
RELEASE_NOTES could just be a flag that the changelist is important enough to warrant presence in release notes, rather than a container for text to put in the release notes. In the end the release notes need to be wrangled into human-readable form anyhow. -scott --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
