On Apr 23, 2013, at 11:01 AM, Michael Sneddon <mwsneddon@lbl.gov> wrote:

Perhaps in the future we should always include a link to this page in the emails that first announce the next build?  I have the impression that most developers have no idea that this page exists, and probably won't remember to check it before a build unless we explicitly tell them to.

Yes, I agree.

Mike, can you look through the page and make sure it's complete and up to date?

Nomi

-michael

On Tue, Apr 23, 2013 at 8:09 AM, Nomi Harris <nlharris@lbl.gov> wrote:

On Apr 23, 2013, at 8:06 AM, "Land, Miriam L." <landml@ornl.gov> wrote:

> I believe that the guidelines already exist:
>
> https://trac.kbase.us/projects/kbase/wiki/TechDocChecking
>
> Miriam
>
> From: Michael Sneddon <mwsneddon@lbl.gov<mailto:mwsneddon@lbl.gov>>
> Date: Monday, April 22, 2013 3:58 PM
> To: Nomi Harris <nlharris@lbl.gov<mailto:nlharris@lbl.gov>>
> Cc: Miriam Land <landml@ornl.gov<mailto:landml@ornl.gov>>, "release-team@kbase.us<mailto:release-team@kbase.us>" <release-team@kbase.us<mailto:release-team@kbase.us>>
> 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.

This exists as well:
https://trac.kbase.us/projects/kbase/wiki/StandardDocuments

We should check that document and make sure it's up-to-date and then send out a reminder to the developers.

        Nomi

> 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 <nlharris@lbl.gov<mailto:nlharris@lbl.gov>> 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." <landml@ornl.gov<mailto:landml@ornl.gov>> 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
>> _