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

Re: [Release-team] Tech doc testing--need to send out failure notices?
by Land, Miriam L. 31 Jan '13

31 Jan '13

Nomi, On 1/31/13 1:19 AM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: >I checked the API docs. 8 of the 11 modules failed, but I notice that >most of these failed to pass initial deploy, so I guess they never got to >the "make deploy-docs" part of the build process. I don't need to notify >the authors of those modules about their tech doc failure when they >failed deploy, do I? I wouldn't think so. >The only module that passed deploy and testing that failed doc was >sim_service, which still doesn't have a deploy-docs target. I think its >author has been busy with other stuff. :-) Yeah, probably busy. >KBaseFBAModeling passed tech doc but failed initial testing. >protein_info_service passed tech doc but failed initial deploy. >Only ONE module passed everything so far: translation. Considering its history, that is a big success. Miriam > Nomi > >_______________________________________________ >Release-team mailing list >Release-team(a)lists.kbase.us >https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] Adding columns to services spreadsheet
by Elizabeth M. Glass 31 Jan '13

31 Jan '13

Can we also add in a column on what science domains these services work for? M, MC, P Elizabeth ----- Original Message ----- From: Thomas Brettin <brettin(a)mcs.anl.gov> To: Miriam L. Land <landml(a)ornl.gov> Cc: release-team(a)lists.kbase.us, Nomi Harris <nlharris(a)lbl.gov> Sent: Thu, 31 Jan 2013 07:09:21 -0600 (CST) Subject: Re: [Release-team] Adding columns to services spreadsheet I want to keep all tabs. I plan to mine this data for research on the progression of the development of a release infrastructure. Tom On Jan 31, 2013, at 7:05 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: > I'm in favor of a master tab. It would be very useful when I need to look > up something that was somewhere in an earlier build. > > I also don't have a problem deleting the tabs that came before Nov Build, > as long as we capture information on old modules that may come up again. > > I think the git repo is a great place to start parsing out the > descriptions. > > Until the redeploy happens this morning, I have time to get this started. > > Miriam > > On 1/30/13 5:50 PM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: > >> Right, I don't want to add another doc either! That's why I was asking if >> I could just add these two columns to the Services doc. I think they'd be >> useful to the people who are on the Build teams as well (maybe not so >> much to the people on the release team, since we already pretty much know >> the info that will be in those columns). >> I'm ok with either adding it to the Feb tab or making a new "master" tab. >> Nomi Harris >> Project Manager, KBase >> >> On Jan 30, 2013, at 1:33 PM, Dan Olson <dolson(a)mcs.anl.gov> wrote: >> >>> I'm all for adding a "master" tab to the services spreadsheet with the >>> static information that doesn't change every release. >>> >>> I really don't want to add another doc - right now we have - >>> A punch list doc >>> An email template doc >>> A trac wiki page >>> A services spreadsheet >>> >>> As time goes on the more info repositories we have the more opportunity >>> for them >>> to diverge and confusion to occur. >>> >>> ----- Original Message ----- >>>> From: "Miriam L. Land" <landml(a)ornl.gov> >>>> To: "Nomi Harris" <nlharris(a)lbl.gov>, release-team(a)lists.kbase.us >>>> Sent: Wednesday, January 30, 2013 3:25:48 PM >>>> Subject: Re: [Release-team] Adding columns to services spreadsheet >>>> >>>> Would it make sense to put the common name, repo name, contact(s), >>>> and >>>> description in a doc by itself? It could be cumulative across all >>>> releases. >>>> >>>> Miriam >>>> >>>> On 1/30/13 3:39 PM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: >>>> >>>>> Today I talked to Elizabeth, who is starting to work on materials >>>>> for the >>>>> User Zone on the website, which will include tutorials, a new User >>>>> Guide, >>>>> and more. She is also helping to write the text about the individual >>>>> services that is currently on >>>>> http://www.kbase.us/developer-zone/services/ . >>>>> Elizabeth asked me for two pieces of information for each service: >>>>> the >>>>> git repo name and corresponding "human language" name of each >>>>> service >>>>> (for example, Central Store Service is in the kb_seed repo--you'd >>>>> never >>>>> guess that if you didn't already know), and also whether the service >>>>> is >>>>> internal-only or user-facing. I think this information would be >>>>> useful to >>>>> have on the Services spreadsheet (in fact, that spreadsheet used to >>>>> have >>>>> the human and git repo names for each service, but lost that at some >>>>> point), but it already has a lot of columns, so I'd like permission >>>>> to >>>>> add those two. >>>>> The Feb 4 Major tab >>>>> >>>>> (https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dFp >>>>> paE >>>>> JzOUdfMV8zN0Y3Vm5YM095aWc#gid=14) is empty so far, so maybe we can >>>>> start >>>>> from scratch and think about what columns make sense. There were >>>>> some on >>>>> the previous tabs that we probably don't need anymore. >>>>> Thanks, >>>>> Nomi Harris >>>>> Project Manager, KBase >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >> >> _______________________________________________ >> 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 Thomas Brettin 865-603-7760 (cell) brettin(a)mcs.anl.gov _______________________________________________ Release-team mailing list Release-team(a)lists.kbase.us https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] Minor release?
by Thomas Brettin 31 Jan '13

31 Jan '13

Yes, unless someone objects. Tom On Jan 30, 2013, at 2:08 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: > Did we officially decide not to do a minor release based on last week's mini-build, and just to wait for the full build/release? > Nomi > Thomas Brettin 865-603-7760 (cell) brettin(a)mcs.anl.gov

1 0

Re: [Release-team] Adding columns to services spreadsheet
by Thomas Brettin 31 Jan '13

31 Jan '13

I want to keep all tabs. I plan to mine this data for research on the progression of the development of a release infrastructure. Tom On Jan 31, 2013, at 7:05 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: > I'm in favor of a master tab. It would be very useful when I need to look > up something that was somewhere in an earlier build. > > I also don't have a problem deleting the tabs that came before Nov Build, > as long as we capture information on old modules that may come up again. > > I think the git repo is a great place to start parsing out the > descriptions. > > Until the redeploy happens this morning, I have time to get this started. > > Miriam > > On 1/30/13 5:50 PM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: > >> Right, I don't want to add another doc either! That's why I was asking if >> I could just add these two columns to the Services doc. I think they'd be >> useful to the people who are on the Build teams as well (maybe not so >> much to the people on the release team, since we already pretty much know >> the info that will be in those columns). >> I'm ok with either adding it to the Feb tab or making a new "master" tab. >> Nomi Harris >> Project Manager, KBase >> >> On Jan 30, 2013, at 1:33 PM, Dan Olson <dolson(a)mcs.anl.gov> wrote: >> >>> I'm all for adding a "master" tab to the services spreadsheet with the >>> static information that doesn't change every release. >>> >>> I really don't want to add another doc - right now we have - >>> A punch list doc >>> An email template doc >>> A trac wiki page >>> A services spreadsheet >>> >>> As time goes on the more info repositories we have the more opportunity >>> for them >>> to diverge and confusion to occur. >>> >>> ----- Original Message ----- >>>> From: "Miriam L. Land" <landml(a)ornl.gov> >>>> To: "Nomi Harris" <nlharris(a)lbl.gov>, release-team(a)lists.kbase.us >>>> Sent: Wednesday, January 30, 2013 3:25:48 PM >>>> Subject: Re: [Release-team] Adding columns to services spreadsheet >>>> >>>> Would it make sense to put the common name, repo name, contact(s), >>>> and >>>> description in a doc by itself? It could be cumulative across all >>>> releases. >>>> >>>> Miriam >>>> >>>> On 1/30/13 3:39 PM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: >>>> >>>>> Today I talked to Elizabeth, who is starting to work on materials >>>>> for the >>>>> User Zone on the website, which will include tutorials, a new User >>>>> Guide, >>>>> and more. She is also helping to write the text about the individual >>>>> services that is currently on >>>>> http://www.kbase.us/developer-zone/services/ . >>>>> Elizabeth asked me for two pieces of information for each service: >>>>> the >>>>> git repo name and corresponding "human language" name of each >>>>> service >>>>> (for example, Central Store Service is in the kb_seed repo--you'd >>>>> never >>>>> guess that if you didn't already know), and also whether the service >>>>> is >>>>> internal-only or user-facing. I think this information would be >>>>> useful to >>>>> have on the Services spreadsheet (in fact, that spreadsheet used to >>>>> have >>>>> the human and git repo names for each service, but lost that at some >>>>> point), but it already has a lot of columns, so I'd like permission >>>>> to >>>>> add those two. >>>>> The Feb 4 Major tab >>>>> >>>>> (https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dFp >>>>> paE >>>>> JzOUdfMV8zN0Y3Vm5YM095aWc#gid=14) is empty so far, so maybe we can >>>>> start >>>>> from scratch and think about what columns make sense. There were >>>>> some on >>>>> the previous tabs that we probably don't need anymore. >>>>> Thanks, >>>>> Nomi Harris >>>>> Project Manager, KBase >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >> >> _______________________________________________ >> 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 Thomas Brettin 865-603-7760 (cell) brettin(a)mcs.anl.gov

1 0

Re: [Release-team] Adding columns to services spreadsheet
by Land, Miriam L. 31 Jan '13

31 Jan '13

I'm in favor of a master tab. It would be very useful when I need to look up something that was somewhere in an earlier build. I also don't have a problem deleting the tabs that came before Nov Build, as long as we capture information on old modules that may come up again. I think the git repo is a great place to start parsing out the descriptions. Until the redeploy happens this morning, I have time to get this started. Miriam On 1/30/13 5:50 PM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: >Right, I don't want to add another doc either! That's why I was asking if >I could just add these two columns to the Services doc. I think they'd be >useful to the people who are on the Build teams as well (maybe not so >much to the people on the release team, since we already pretty much know >the info that will be in those columns). >I'm ok with either adding it to the Feb tab or making a new "master" tab. > Nomi Harris > Project Manager, KBase > >On Jan 30, 2013, at 1:33 PM, Dan Olson <dolson(a)mcs.anl.gov> wrote: > >> I'm all for adding a "master" tab to the services spreadsheet with the >> static information that doesn't change every release. >> >> I really don't want to add another doc - right now we have - >> A punch list doc >> An email template doc >> A trac wiki page >> A services spreadsheet >> >> As time goes on the more info repositories we have the more opportunity >>for them >> to diverge and confusion to occur. >> >> ----- Original Message ----- >>> From: "Miriam L. Land" <landml(a)ornl.gov> >>> To: "Nomi Harris" <nlharris(a)lbl.gov>, release-team(a)lists.kbase.us >>> Sent: Wednesday, January 30, 2013 3:25:48 PM >>> Subject: Re: [Release-team] Adding columns to services spreadsheet >>> >>> Would it make sense to put the common name, repo name, contact(s), >>> and >>> description in a doc by itself? It could be cumulative across all >>> releases. >>> >>> Miriam >>> >>> On 1/30/13 3:39 PM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: >>> >>>> Today I talked to Elizabeth, who is starting to work on materials >>>> for the >>>> User Zone on the website, which will include tutorials, a new User >>>> Guide, >>>> and more. She is also helping to write the text about the individual >>>> services that is currently on >>>> http://www.kbase.us/developer-zone/services/ . >>>> Elizabeth asked me for two pieces of information for each service: >>>> the >>>> git repo name and corresponding "human language" name of each >>>> service >>>> (for example, Central Store Service is in the kb_seed repo--you'd >>>> never >>>> guess that if you didn't already know), and also whether the service >>>> is >>>> internal-only or user-facing. I think this information would be >>>> useful to >>>> have on the Services spreadsheet (in fact, that spreadsheet used to >>>> have >>>> the human and git repo names for each service, but lost that at some >>>> point), but it already has a lot of columns, so I'd like permission >>>> to >>>> add those two. >>>> The Feb 4 Major tab >>>> >>>>(https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dFp >>>>paE >>>> JzOUdfMV8zN0Y3Vm5YM095aWc#gid=14) is empty so far, so maybe we can >>>> start >>>> from scratch and think about what columns make sense. There were >>>> some on >>>> the previous tabs that we probably don't need anymore. >>>> Thanks, >>>> Nomi Harris >>>> Project Manager, KBase >>>> >>>> _______________________________________________ >>>> 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 >>> > >_______________________________________________ >Release-team mailing list >Release-team(a)lists.kbase.us >https://lists.kbase.us/mailman/listinfo/release-team

1 0

Tech doc testing--need to send out failure notices?
by Nomi Harris 31 Jan '13

31 Jan '13

I checked the API docs. 8 of the 11 modules failed, but I notice that most of these failed to pass initial deploy, so I guess they never got to the "make deploy-docs" part of the build process. I don't need to notify the authors of those modules about their tech doc failure when they failed deploy, do I? The only module that passed deploy and testing that failed doc was sim_service, which still doesn't have a deploy-docs target. I think its author has been busy with other stuff. :-) KBaseFBAModeling passed tech doc but failed initial testing. protein_info_service passed tech doc but failed initial deploy. Only ONE module passed everything so far: translation. Nomi

1 0

Getting code into the "full release"--what's the deadline?
by Nomi Harris 31 Jan '13

31 Jan '13

Hi Tom, I would like a clearer definition of how/when we are going to roll out the "full release" after next week's full build. In an ideal world, everything that we wanted to show in our Feb 25th demos would be checked into git by this Friday, tested next week during the Build, and then released in one big beautiful release the following week, after which we'd only re-release modules that had catastrophic bugs found and fixed, until some time in March when we'd do another minor build/release. However, I know that some (all?) of the domains are planning to finish writing code for the demos right up till the bitter end, which leaves us in an awkward position, because we can't have people checking in code on midnight on Sunday the 24th of Feb and expecting their code to make it into "the" release--we'd have no time to test and release it. So clearly we need to establish a deadline for getting stuff into the big Feb release--and I don't think telling people that tomorrow is the deadline would go over too well. What were you envisioning? Nomi

1 0

Build week team assignments
by Nomi Harris 30 Jan '13

30 Jan '13

Tom and I made some semi-arbitrary new assignments to teams (which included making up some new teams, such as GUI testing). Please look at https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dHF4Nlho… when you get a chance and comment on (or just change) any assignments you don't like. I guess we should find someone to lead the GUI testing team. (The other new teams are small enough that I'm not sure we need to bother designating a lead, though maybe it would be a good idea anyway.) Nomi Harris Project Manager, KBase

1 0

Re: [Release-team] Adding columns to services spreadsheet
by Elizabeth M. Glass 30 Jan '13

30 Jan '13

My preference is for a master tab on the same document (but am fine with either). ----- Original Message ----- From: Nomi Harris <nlharris(a)lbl.gov> To: Dan Olson <dolson(a)mcs.anl.gov> Cc: release-team(a)lists.kbase.us Sent: Wed, 30 Jan 2013 16:50:42 -0600 (CST) Subject: Re: [Release-team] Adding columns to services spreadsheet Right, I don't want to add another doc either! That's why I was asking if I could just add these two columns to the Services doc. I think they'd be useful to the people who are on the Build teams as well (maybe not so much to the people on the release team, since we already pretty much know the info that will be in those columns). I'm ok with either adding it to the Feb tab or making a new "master" tab. Nomi Harris Project Manager, KBase On Jan 30, 2013, at 1:33 PM, Dan Olson <dolson(a)mcs.anl.gov> wrote: > I'm all for adding a "master" tab to the services spreadsheet with the > static information that doesn't change every release. > > I really don't want to add another doc - right now we have - > A punch list doc > An email template doc > A trac wiki page > A services spreadsheet > > As time goes on the more info repositories we have the more opportunity for them > to diverge and confusion to occur. > > ----- Original Message ----- >> From: "Miriam L. Land" <landml(a)ornl.gov> >> To: "Nomi Harris" <nlharris(a)lbl.gov>, release-team(a)lists.kbase.us >> Sent: Wednesday, January 30, 2013 3:25:48 PM >> Subject: Re: [Release-team] Adding columns to services spreadsheet >> >> Would it make sense to put the common name, repo name, contact(s), >> and >> description in a doc by itself? It could be cumulative across all >> releases. >> >> Miriam >> >> On 1/30/13 3:39 PM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: >> >>> Today I talked to Elizabeth, who is starting to work on materials >>> for the >>> User Zone on the website, which will include tutorials, a new User >>> Guide, >>> and more. She is also helping to write the text about the individual >>> services that is currently on >>> http://www.kbase.us/developer-zone/services/ . >>> Elizabeth asked me for two pieces of information for each service: >>> the >>> git repo name and corresponding "human language" name of each >>> service >>> (for example, Central Store Service is in the kb_seed repo--you'd >>> never >>> guess that if you didn't already know), and also whether the service >>> is >>> internal-only or user-facing. I think this information would be >>> useful to >>> have on the Services spreadsheet (in fact, that spreadsheet used to >>> have >>> the human and git repo names for each service, but lost that at some >>> point), but it already has a lot of columns, so I'd like permission >>> to >>> add those two. >>> The Feb 4 Major tab >>> (https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dFppaE >>> JzOUdfMV8zN0Y3Vm5YM095aWc#gid=14) is empty so far, so maybe we can >>> start >>> from scratch and think about what columns make sense. There were >>> some on >>> the previous tabs that we probably don't need anymore. >>> Thanks, >>> Nomi Harris >>> Project Manager, KBase >>> >>> _______________________________________________ >>> 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 >> _______________________________________________ Release-team mailing list Release-team(a)lists.kbase.us https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] Adding columns to services spreadsheet
by Nomi Harris 30 Jan '13

30 Jan '13

Right, I don't want to add another doc either! That's why I was asking if I could just add these two columns to the Services doc. I think they'd be useful to the people who are on the Build teams as well (maybe not so much to the people on the release team, since we already pretty much know the info that will be in those columns). I'm ok with either adding it to the Feb tab or making a new "master" tab. Nomi Harris Project Manager, KBase On Jan 30, 2013, at 1:33 PM, Dan Olson <dolson(a)mcs.anl.gov> wrote: > I'm all for adding a "master" tab to the services spreadsheet with the > static information that doesn't change every release. > > I really don't want to add another doc - right now we have - > A punch list doc > An email template doc > A trac wiki page > A services spreadsheet > > As time goes on the more info repositories we have the more opportunity for them > to diverge and confusion to occur. > > ----- Original Message ----- >> From: "Miriam L. Land" <landml(a)ornl.gov> >> To: "Nomi Harris" <nlharris(a)lbl.gov>, release-team(a)lists.kbase.us >> Sent: Wednesday, January 30, 2013 3:25:48 PM >> Subject: Re: [Release-team] Adding columns to services spreadsheet >> >> Would it make sense to put the common name, repo name, contact(s), >> and >> description in a doc by itself? It could be cumulative across all >> releases. >> >> Miriam >> >> On 1/30/13 3:39 PM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: >> >>> Today I talked to Elizabeth, who is starting to work on materials >>> for the >>> User Zone on the website, which will include tutorials, a new User >>> Guide, >>> and more. She is also helping to write the text about the individual >>> services that is currently on >>> http://www.kbase.us/developer-zone/services/ . >>> Elizabeth asked me for two pieces of information for each service: >>> the >>> git repo name and corresponding "human language" name of each >>> service >>> (for example, Central Store Service is in the kb_seed repo--you'd >>> never >>> guess that if you didn't already know), and also whether the service >>> is >>> internal-only or user-facing. I think this information would be >>> useful to >>> have on the Services spreadsheet (in fact, that spreadsheet used to >>> have >>> the human and git repo names for each service, but lost that at some >>> point), but it already has a lot of columns, so I'd like permission >>> to >>> add those two. >>> The Feb 4 Major tab >>> (https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dFppaE >>> JzOUdfMV8zN0Y3Vm5YM095aWc#gid=14) is empty so far, so maybe we can >>> start >>> from scratch and think about what columns make sense. There were >>> some on >>> the previous tabs that we probably don't need anymore. >>> Thanks, >>> Nomi Harris >>> Project Manager, KBase >>> >>> _______________________________________________ >>> 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