I believe that the guidelines already exist: https://trac.kbase.us/projects/kbase/wiki/TechDocChecking Miriam From: Michael Sneddon <[email protected]<mailto:[email protected]>> Date: Monday, April 22, 2013 3:58 PM To: Nomi Harris <[email protected]<mailto:[email protected]>> Cc: Miriam Land <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [Release-team] release notes I don't think it has been strictly enforced in the past, but I also think we should start requiring it. I know I completely forgot to update the release notes for Trees, which I should have done... Perhaps we should provide a very simple module checklist of what we require for a module to enter the release process, really just as a guideline to help developers remember everything that needs to be done. Some of us had started adopting the convention of placing notes in a file named RELEASE_NOTES.txt in the root directory of each module. On Mon, Apr 22, 2013 at 12:52 PM, Nomi Harris <[email protected]<mailto:[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]<mailto:[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 _______________________________________________ Release-team mailing list [email protected]<mailto:[email protected]> https://lists.kbase.us/mailman/listinfo/release-team

_______________________________________________ Release-team mailing list [email protected]<mailto:[email protected]> https://lists.kbase.us/mailman/listinfo/release-team