- Release-team - mailman3.cels.anl.gov

Re: [Release-team] release notes
by Land, Miriam L. 24 Apr '13

24 Apr '13

There are probably several pages that could be useful reminders. Miriam From: Michael Sneddon <mwsneddon(a)lbl.gov<mailto:[email protected]>> Date: Tuesday, April 23, 2013 2:01 PM To: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> Cc: "release-team(a)kbase.us<mailto:[email protected]>" <release-team(a)kbase.us<mailto:[email protected]>> Subject: Re: [Release-team] release notes 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. -michael On Tue, Apr 23, 2013 at 8:09 AM, Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> wrote: On Apr 23, 2013, at 8:06 AM, "Land, Miriam L." <landml(a)ornl.gov<mailto:[email protected]>> wrote: > I believe that the guidelines already exist: > > https://trac.kbase.us/projects/kbase/wiki/TechDocChecking > > Miriam > > From: Michael Sneddon <mwsneddon(a)lbl.gov<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> > Date: Monday, April 22, 2013 3:58 PM > To: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>> > Cc: Miriam Land <landml(a)ornl.gov<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>>, "release-team(a)kbase.us<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>>" <release-team(a)kbase.us<mailto:[email protected]><mailto:[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. 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(a)lbl.gov<mailto:[email protected]><mailto:[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." <landml(a)ornl.gov<mailto:[email protected]><mailto:[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 >> Release-team(a)lists.kbase.us<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> >> https://lists.kbase.us/mailman/listinfo/release-team > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us<mailto:[email protected]><mailto:[email protected]<mailto:[email protected]>> > https://lists.kbase.us/mailman/listinfo/release-team > _______________________________________________ Release-team mailing list Release-team(a)lists.kbase.us<mailto:[email protected]> https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] Minor release punch list
by Thomas Brettin 24 Apr '13

24 Apr '13

I agree that it might not make sense to physically check things off in the future as long as the major transitions can happen. On Apr 24, 2013, at 12:15 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > Dear release team, > As requested during yesterday's release meeting, I have created a master copy of the Minor Release Punch List so that we can then leave it alone and make copies of it to use (and check off items) during each minor release. > I'm still not convinced that we need to go through the trouble of checking off each step, but maybe it makes sense for now. > I made some (mostly minor) edits and added some comments/questions. Please take a look at https://docs.google.com/document/d/1Tf7rEc2V0-3pIBhxzbkjLdzyF3Xf2MgoI1WnT_u… > and see if it looks ok (and if you have any answers to the questions). If so, I'll create an April 22 version and we can all start ticking off items. > Nomi > > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team

1 0

Minor release punch list
by Nomi Harris 24 Apr '13

24 Apr '13

Dear release team, As requested during yesterday's release meeting, I have created a master copy of the Minor Release Punch List so that we can then leave it alone and make copies of it to use (and check off items) during each minor release. I'm still not convinced that we need to go through the trouble of checking off each step, but maybe it makes sense for now. I made some (mostly minor) edits and added some comments/questions. Please take a look at https://docs.google.com/document/d/1Tf7rEc2V0-3pIBhxzbkjLdzyF3Xf2MgoI1WnT_u… and see if it looks ok (and if you have any answers to the questions). If so, I'll create an April 22 version and we can all start ticking off items. Nomi

1 0

Re: [Release-team] configuring test module deployments to point to dependent service urls
by Thomas Brettin 23 Apr '13

23 Apr '13

Yes, and I think Gavin prototyped something. I am putting this one on the list for a build sprint. On Apr 23, 2013, at 7:44 PM, Michael Sneddon <mwsneddon(a)lbl.gov> wrote: > It seems like we will ultimately need to specify not just the dependent module in DEPENDENCIES, but also the version of the dependent module that is required, and then actually figure out a way to resolve these dependencies to make sure deployed modules (and test deploys) are pointing to the correct endpoints, and that these endpoints will all be compatible once we push new versions to production. I know Gavin has been thinking lately about how to approach these issues too, so we may want to bring him into these discussions as well.

1 0

Re: [Release-team] configuring test module deployments to point to dependent service urls
by Dan Olson 23 Apr '13

23 Apr '13

In the test environment "kbase.us" points to the test deployment. It's all done with /etc/hosts. ----- Original Message ----- > From: "Michael Sneddon" <mwsneddon(a)lbl.gov> > To: release-team(a)kbase.us > Sent: Tuesday, April 23, 2013 7:44:09 PM > Subject: [Release-team] configuring test module deployments to point to dependent service urls > > > > > I'm digging though some of the test deployments, and it occurs to me > that for Trees, at least, the test deployment looks like it is > pointing to the production url of the ERDB service, not the new test > deployment of the ERDB service. This URL is configurable from the > deploy.cfg file, but as far as I know we don't have an official > process of changing dependent service endpoints during a test or > during a migration to production. > > > Everything still works for this minor release, because there were no > new changes to the ERDB module that affect the Tree service. > However, I think this is clearly a more general problem that we > haven't solved. If the new version of Trees depended on a new > version of the ERDB service that was not in production, how would we > configure the modules to be sure that it is tested correctly? Or > worse, if the new ERDB service had last minute changes that make it > incompatible with the new version of Trees, but all the test > deployments of Trees was still pointing to production urls, we > wouldn't catch the error until *after* we pushed everything out to > production. > > > It seems like we will ultimately need to specify not just the > dependent module in DEPENDENCIES, but also the version of the > dependent module that is required, and then actually figure out a > way to resolve these dependencies to make sure deployed modules (and > test deploys) are pointing to the correct endpoints, and that these > endpoints will all be compatible once we push new versions to > production. I know Gavin has been thinking lately about how to > approach these issues too, so we may want to bring him into these > discussions as well. > > > Working out these issues more thoroughly might be a good use of some > our time during the May meeting. > > > Any thoughts on this? Is there something I'm missing? > > > -michael > > > > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team >

1 0

configuring test module deployments to point to dependent service urls
by Michael Sneddon 23 Apr '13

23 Apr '13

I'm digging though some of the test deployments, and it occurs to me that for Trees, at least, the test deployment looks like it is pointing to the production url of the ERDB service, not the new test deployment of the ERDB service. This URL is configurable from the deploy.cfg file, but as far as I know we don't have an official process of changing dependent service endpoints during a test or during a migration to production. Everything still works for this minor release, because there were no new changes to the ERDB module that affect the Tree service. However, I think this is clearly a more general problem that we haven't solved. If the new version of Trees depended on a new version of the ERDB service that was not in production, how would we configure the modules to be sure that it is tested correctly? Or worse, if the new ERDB service had last minute changes that make it incompatible with the new version of Trees, but all the test deployments of Trees was still pointing to production urls, we wouldn't catch the error until *after* we pushed everything out to production. It seems like we will ultimately need to specify not just the dependent module in DEPENDENCIES, but also the version of the dependent module that is required, and then actually figure out a way to resolve these dependencies to make sure deployed modules (and test deploys) are pointing to the correct endpoints, and that these endpoints will all be compatible once we push new versions to production. I know Gavin has been thinking lately about how to approach these issues too, so we may want to bring him into these discussions as well. Working out these issues more thoroughly might be a good use of some our time during the May meeting. Any thoughts on this? Is there something I'm missing? -michael

1 0

Re: [Release-team] release notes
by Michael Sneddon 23 Apr '13

23 Apr '13

Just had a look, and overall things seem to be fairly up-to-date with the current process, as far as I can tell, although we could probably do a better job with the specifications in some of the pages that this main page links to. I did take a stab at more clearly stating what (currently) is absolutely required for us to deploy vs. what we hope will soon be required (e.g. user manuals). -michael On Tue, Apr 23, 2013 at 11:17 AM, Michael Sneddon <mwsneddon(a)lbl.gov> wrote: > Sure, I'll take a closer look. > > > On Tue, Apr 23, 2013 at 11:07 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > >> On Apr 23, 2013, at 11:01 AM, Michael Sneddon <mwsneddon(a)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(a)lbl.gov> wrote: >> >>> On Apr 23, 2013, at 8:06 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: >>> >>> > I believe that the guidelines already exist: >>> > >>> > https://trac.kbase.us/projects/kbase/wiki/TechDocChecking >>> > >>> > Miriam >>> > >>> > From: Michael Sneddon <mwsneddon(a)lbl.gov<mailto:[email protected]>> >>> > Date: Monday, April 22, 2013 3:58 PM >>> > To: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> >>> > Cc: Miriam Land <landml(a)ornl.gov<mailto:[email protected]>>, " >>> release-team(a)kbase.us<mailto:[email protected]>" < >>> release-team(a)kbase.us<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. >>> >>> 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(a)lbl.gov >>> <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." <landml(a)ornl.gov >>> <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 >>> >> _ >>> >> >

1 0

Re: [Release-team] release notes
by Michael Sneddon 23 Apr '13

23 Apr '13

Sure, I'll take a closer look. On Tue, Apr 23, 2013 at 11:07 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > On Apr 23, 2013, at 11:01 AM, Michael Sneddon <mwsneddon(a)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(a)lbl.gov> wrote: > >> On Apr 23, 2013, at 8:06 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: >> >> > I believe that the guidelines already exist: >> > >> > https://trac.kbase.us/projects/kbase/wiki/TechDocChecking >> > >> > Miriam >> > >> > From: Michael Sneddon <mwsneddon(a)lbl.gov<mailto:[email protected]>> >> > Date: Monday, April 22, 2013 3:58 PM >> > To: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> >> > Cc: Miriam Land <landml(a)ornl.gov<mailto:[email protected]>>, " >> release-team(a)kbase.us<mailto:[email protected]>" < >> release-team(a)kbase.us<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. >> >> 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(a)lbl.gov<mailto: >> nlharris(a)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(a)ornl.gov >> <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 >> >> _ >> >

1 0

Re: [Release-team] release notes
by Nomi Harris 23 Apr '13

23 Apr '13

On Apr 23, 2013, at 11:01 AM, Michael Sneddon <mwsneddon(a)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(a)lbl.gov> wrote: > On Apr 23, 2013, at 8:06 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: > > > I believe that the guidelines already exist: > > > > https://trac.kbase.us/projects/kbase/wiki/TechDocChecking > > > > Miriam > > > > From: Michael Sneddon <mwsneddon(a)lbl.gov<mailto:[email protected]>> > > Date: Monday, April 22, 2013 3:58 PM > > To: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> > > Cc: Miriam Land <landml(a)ornl.gov<mailto:[email protected]>>, "release-team(a)kbase.us<mailto:[email protected]>" <release-team(a)kbase.us<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. > > 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(a)lbl.gov<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." <landml(a)ornl.gov<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 > >> _

1 0

Re: [Release-team] release notes
by Michael Sneddon 23 Apr '13

23 Apr '13

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. -michael On Tue, Apr 23, 2013 at 8:09 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > On Apr 23, 2013, at 8:06 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: > > > I believe that the guidelines already exist: > > > > https://trac.kbase.us/projects/kbase/wiki/TechDocChecking > > > > Miriam > > > > From: Michael Sneddon <mwsneddon(a)lbl.gov<mailto:[email protected]>> > > Date: Monday, April 22, 2013 3:58 PM > > To: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> > > Cc: Miriam Land <landml(a)ornl.gov<mailto:[email protected]>>, " > release-team(a)kbase.us<mailto:[email protected]>" < > release-team(a)kbase.us<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. > > 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(a)lbl.gov<mailto: > nlharris(a)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(a)ornl.gov<mailto: > landml(a)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 > >> _______________________________________________ > >> Release-team mailing list > >> Release-team(a)lists.kbase.us<mailto:[email protected]> > >> https://lists.kbase.us/mailman/listinfo/release-team > > > > _______________________________________________ > > Release-team mailing list > > Release-team(a)lists.kbase.us<mailto:[email protected]> > > https://lists.kbase.us/mailman/listinfo/release-team > > > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team >

1 0