Well, we had a (somewhat arbitrary) convention that release notes are put in a file called RELEASE_NOTES.txt in the main directory of the git repo. We introduced the idea of release notes at the November build but didn't end up enforcing them because release notes are not very useful for an initial release. They are, however, very useful for subsequent releases, like this one. I don't have a strong opinion about where the release notes should go or what they should be called, or whether they should all be concatenated in one big file or be separate files for each release. Maybe Mike has opinions? However, I do think the release notes should be compiled by the developers, not by the build teams. Only the developers know exactly what they've changed. Nomi On Apr 22, 2013, at 12:54 PM, "Land, Miriam L." <[email protected]> wrote:

If we had them, where is the right place to document and communicate them? At times we have used the spreadsheet for this.

Miriam

On 4/22/13 3:52 PM, "Nomi Harris" <[email protected]> wrote:

...

Yes--I didn't get a chance to discuss this during today's meeting but I would like to see release notes for the services that are included in this minor release. This would be useful both internally (for testing, as Miriam notes) and externally (so users know what has changed). Nomi

On Apr 22, 2013, at 12:47 PM, "Land, Miriam L." <[email protected]> wrote:

...

All,

Do we have anything like release notes for this build? For testing purposes, it would be nice to have a list of things to specifically test for.

Miriam