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

Re: [Release-team] [Kbase-devel] starting a new minor release
by Thomas Brettin 22 Apr '13

22 Apr '13

could we get genome_annotation if if we can make some changes before noon? t On Apr 22, 2013, at 9:38 AM, Dan Olson <dolson(a)mcs.anl.gov> wrote: > The final list is: > > Requested: > invocation > auth > auth_service > protein_info_service > trees > > Required deps: > typecomp > kb_seed > erdb_service > kbapi_common > > > ----- Original Message ----- >> From: "Dan Olson" <dolson(a)mcs.anl.gov> >> To: "Thomas Brettin" <brettin(a)mcs.anl.gov> >> Cc: "kbase-devel(a)lists.kbase.us devel" <kbase-devel(a)lists.kbase.us>, release-team(a)lists.kbase.us >> Sent: Monday, April 22, 2013 9:32:39 AM >> Subject: Re: [Release-team] starting a new minor release >> >> I'm starting this deploy in our test environment right now. >> >> ----- Original Message ----- >>> From: "Thomas Brettin" <brettin(a)mcs.anl.gov> >>> To: "Thomas Brettin" <brettin(a)mcs.anl.gov> >>> Cc: "kbase-devel(a)lists.kbase.us devel" >>> <kbase-devel(a)lists.kbase.us>, release-team(a)lists.kbase.us >>> Sent: Monday, April 22, 2013 4:50:18 AM >>> Subject: Re: [Release-team] starting a new minor release >>> >>> These are the services that were requested for release this week >>> >>> Git Repository Requestor >>> >>> invocation Tom >>> auth Steve >>> auth_service Steve >>> protein_info Keith >>> trees Mike >>> >>> >>> Tom >>> >>> On Apr 18, 2013, at 11:10 AM, Thomas Brettin <brettin(a)mcs.anl.gov> >>> wrote: >>> >>>> We're going to start a minor release on Monday. Right now, we >>>> have >>>> the Invocation Service scheduled. >>>> >>>> Any module that would benefit from having a redeployment to >>>> production with updated service URLS, this is a good chance to >>>> get >>>> that done. >>>> >>>> Let me know if you want your module on the schedule. >>>> >>>> Thanks, >>>> Tom >>> >>> _______________________________________________ >>> Release-team mailing list >>> Release-team(a)lists.kbase.us >>> 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 >> > _______________________________________________ > Kbase-devel mailing list > Kbase-devel(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/kbase-devel

1 0

Re: [Release-team] starting a new minor release
by Dan Olson 22 Apr '13

22 Apr '13

The final list is: Requested: invocation auth auth_service protein_info_service trees Required deps: typecomp kb_seed erdb_service kbapi_common ----- Original Message ----- > From: "Dan Olson" <dolson(a)mcs.anl.gov> > To: "Thomas Brettin" <brettin(a)mcs.anl.gov> > Cc: "kbase-devel(a)lists.kbase.us devel" <kbase-devel(a)lists.kbase.us>, release-team(a)lists.kbase.us > Sent: Monday, April 22, 2013 9:32:39 AM > Subject: Re: [Release-team] starting a new minor release > > I'm starting this deploy in our test environment right now. > > ----- Original Message ----- > > From: "Thomas Brettin" <brettin(a)mcs.anl.gov> > > To: "Thomas Brettin" <brettin(a)mcs.anl.gov> > > Cc: "kbase-devel(a)lists.kbase.us devel" > > <kbase-devel(a)lists.kbase.us>, release-team(a)lists.kbase.us > > Sent: Monday, April 22, 2013 4:50:18 AM > > Subject: Re: [Release-team] starting a new minor release > > > > These are the services that were requested for release this week > > > > Git Repository Requestor > > > > invocation Tom > > auth Steve > > auth_service Steve > > protein_info Keith > > trees Mike > > > > > > Tom > > > > On Apr 18, 2013, at 11:10 AM, Thomas Brettin <brettin(a)mcs.anl.gov> > > wrote: > > > > > We're going to start a minor release on Monday. Right now, we > > > have > > > the Invocation Service scheduled. > > > > > > Any module that would benefit from having a redeployment to > > > production with updated service URLS, this is a good chance to > > > get > > > that done. > > > > > > Let me know if you want your module on the schedule. > > > > > > Thanks, > > > Tom > > > > _______________________________________________ > > Release-team mailing list > > Release-team(a)lists.kbase.us > > 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

Re: [Release-team] starting a new minor release
by Dan Olson 22 Apr '13

22 Apr '13

I'm starting this deploy in our test environment right now. ----- Original Message ----- > From: "Thomas Brettin" <brettin(a)mcs.anl.gov> > To: "Thomas Brettin" <brettin(a)mcs.anl.gov> > Cc: "kbase-devel(a)lists.kbase.us devel" <kbase-devel(a)lists.kbase.us>, release-team(a)lists.kbase.us > Sent: Monday, April 22, 2013 4:50:18 AM > Subject: Re: [Release-team] starting a new minor release > > These are the services that were requested for release this week > > Git Repository Requestor > > invocation Tom > auth Steve > auth_service Steve > protein_info Keith > trees Mike > > > Tom > > On Apr 18, 2013, at 11:10 AM, Thomas Brettin <brettin(a)mcs.anl.gov> > wrote: > > > We're going to start a minor release on Monday. Right now, we have > > the Invocation Service scheduled. > > > > Any module that would benefit from having a redeployment to > > production with updated service URLS, this is a good chance to get > > that done. > > > > Let me know if you want your module on the schedule. > > > > Thanks, > > Tom > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team >

1 0

Re: [Release-team] starting a new minor release
by Thomas Brettin 22 Apr '13

22 Apr '13

These are the services that were requested for release this week Git Repository Requestor invocation Tom auth Steve auth_service Steve protein_info Keith trees Mike Tom On Apr 18, 2013, at 11:10 AM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > We're going to start a minor release on Monday. Right now, we have the Invocation Service scheduled. > > Any module that would benefit from having a redeployment to production with updated service URLS, this is a good chance to get that done. > > Let me know if you want your module on the schedule. > > Thanks, > Tom

1 0

minor release
by Thomas Brettin 18 Apr '13

18 Apr '13

There is a new tab in KBase Services on gdoc labeled Apr 23 2013 Minor Build. So far, we have 5 modules to redeploy. I know Bob wanted genome_annotation to be redeployed too. Git Repository invocation auth auth_service aux_store protein_info trees

1 0

12:30 -1:00 pm CST Short Prep Meeting
by brettin＠mcs.anl.gov 18 Apr '13

18 Apr '13

The following is a new meeting request: Subject: 12:30 -1:00 pm CST [Release-team] Short Prep Meeting Organizer: brettin(a)mcs.anl.gov Sent By: "India S. Gordon" <igordon(a)cels.anl.gov> Location: 888-850-4523, passcode: 416791, leader passcode (Tom only) 4167913 Time: Monday, April 22, 2013, 12:30:00 PM - 1:00:00 PM GMT -06:00 US/Canada Central Invitees: release-team(a)lists.kbase.us *~*~*~*~*~*~*~*~*~*

1 0

Re: [Release-team] minor release - start of the release notes
by Nomi Harris 18 Apr '13

18 Apr '13

On Apr 18, 2013, at 12:08 PM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > I would like to do a minor release next week. > > The primary target would be the invocation service. The current production invocation service is not aware of all of the commands as new command files were added to services after the last major build. > > Also, what do you guys think about the release engineering team "owning" the release notes? Basically, when we boot up a minor release, those things scheduled for the minor release would have a short sentence like the one above. These could be for internal use only, but I thin it would be good to know in general why something got scheduled for a minor release. Can you clarify what you mean by "owning"? It makes sense for the release team to collect and share (in whatever manner we decide, internal and/or external) the release notes, but I'm not sure how easy it will be for them to actually write the release notes. In the case above, the invocation service, the release team is intimately aware of what's going on with it, but how would the release team be expected to know what changed in all of the other services? If the developers added informative commit messages, it should be possible for the release team to read them all and summarize the changes, but that's a big if. I do think the release notes (at least in some concise form) should be shared publicly on our website so our users know what has changed. It would also be useful for the release team to keep more detailed release notes to help make us more aware of what has changed, for trouble-shooting etc. Nomi

1 0

Re: [Release-team] short prep meeting
by Elizabeth M. Glass 18 Apr '13

18 Apr '13

I will be in flight to DC for the GSC meeting. I can do Tuesday. ----- Original Message ----- From: Thomas Brettin <brettin(a)mcs.anl.gov> To: India Gordon <igordon(a)cels.anl.gov> Cc: release-team(a)lists.kbase.us Sent: Thu, 18 Apr 2013 11:12:13 -0500 (CDT) Subject: [Release-team] short prep meeting Hey all, It would good to sync on Monday if possible shortly after Dan does the first deploy to the test environment. Thanks, Tom _______________________________________________ Release-team mailing list Release-team(a)lists.kbase.us https://lists.kbase.us/mailman/listinfo/release-team

1 0

short prep meeting
by Thomas Brettin 18 Apr '13

18 Apr '13

Hey all, It would good to sync on Monday if possible shortly after Dan does the first deploy to the test environment. Thanks, Tom

1 0

minor release - start of the release notes
by Thomas Brettin 18 Apr '13

18 Apr '13

I would like to do a minor release next week. The primary target would be the invocation service. The current production invocation service is not aware of all of the commands as new command files were added to services after the last major build. Also, what do you guys think about the release engineering team "owning" the release notes? Basically, when we boot up a minor release, those things scheduled for the minor release would have a short sentence like the one above. These could be for internal use only, but I thin it would be good to know in general why something got scheduled for a minor release. t

1 0