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

Re: [Release-team] FW: build team assignments
by Dan Olson 24 Jan '13

24 Jan '13

I should be available at the beginning of this, but I'm going to have to leave about halfway through. ----- Original Message ----- > From: "Miriam L. Land" <landml(a)ornl.gov> > To: release-team(a)lists.kbase.us > Sent: Thursday, January 24, 2013 7:13:55 AM > Subject: [Release-team] FW: build team assignments > > Release Team, > > Tom would like to have a conference call on Friday to discuss team > assignments. Nomi is only available Fri 9-10am PST (11-12 CST, 12-2 > EST). > Tom and I are also available at that time. If you have an interest > in > getting people for your team, please let Tom know of any conflicts. > > Miriam > > On 1/24/13 2:17 AM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: > > >The only time I'm available on Fri is 9-10am PST. Does that work for > >you? > > Nomi > > > >On Jan 23, 2013, at 11:15 PM, Thomas Brettin <Brettin(a)mcs.anl.gov> > >wrote: > > > >> yes, i think we need to have a con-call -- release engineering > >> team -- > >>friday -- to refine and adjust. We also need to do something about > >>the > >>non-performers. > >> > >> tom > >> > >> On Jan 23, 2013, at 11:57 PM, Nomi Harris <nlharris(a)lbl.gov> > >> wrote: > >> > >>> There are still a lot of people not assigned to any team--should > >>> we > >>>talk through the list at some point? > >>> > >>>https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dHF4N > >>>lhocFhjeEk4MFJwNUlQS0Y4OEE#gid=2 > >>> > >>> I added Travis Harrison to my tech doc team, > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team >

1 0

Re: [Release-team] FW: build team assignments
by Elizabeth M. Glass 24 Jan '13

24 Jan '13

I am available. Elizabeth ----- Original Message ----- From: Miriam L. Land <landml(a)ornl.gov> To: release-team(a)lists.kbase.us Sent: Thu, 24 Jan 2013 07:13:55 -0600 (CST) Subject: [Release-team] FW: build team assignments Release Team, Tom would like to have a conference call on Friday to discuss team assignments. Nomi is only available Fri 9-10am PST (11-12 CST, 12-2 EST). Tom and I are also available at that time. If you have an interest in getting people for your team, please let Tom know of any conflicts. Miriam On 1/24/13 2:17 AM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: >The only time I'm available on Fri is 9-10am PST. Does that work for you? > Nomi > >On Jan 23, 2013, at 11:15 PM, Thomas Brettin <Brettin(a)mcs.anl.gov> wrote: > >> yes, i think we need to have a con-call -- release engineering team -- >>friday -- to refine and adjust. We also need to do something about the >>non-performers. >> >> tom >> >> On Jan 23, 2013, at 11:57 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >> >>> There are still a lot of people not assigned to any team--should we >>>talk through the list at some point? >>> >>>https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dHF4N >>>lhocFhjeEk4MFJwNUlQS0Y4OEE#gid=2 >>> >>> I added Travis Harrison to my tech doc team, _______________________________________________ Release-team mailing list Release-team(a)lists.kbase.us https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] FW: build team assignments
by Shiran Pasternak 24 Jan '13

24 Jan '13

I have the kbase networks call at 1pm ET so I can only join for the first hour. But I think that's ok. S On Jan 24, 2013, at 8:13 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: > Release Team, > > Tom would like to have a conference call on Friday to discuss team > assignments. Nomi is only available Fri 9-10am PST (11-12 CST, 12-2 EST). > Tom and I are also available at that time. If you have an interest in > getting people for your team, please let Tom know of any conflicts. > > Miriam > > On 1/24/13 2:17 AM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: > >> The only time I'm available on Fri is 9-10am PST. Does that work for you? >> Nomi >> >> On Jan 23, 2013, at 11:15 PM, Thomas Brettin <Brettin(a)mcs.anl.gov> wrote: >> >>> yes, i think we need to have a con-call -- release engineering team -- >>> friday -- to refine and adjust. We also need to do something about the >>> non-performers. >>> >>> tom >>> >>> On Jan 23, 2013, at 11:57 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >>> >>>> There are still a lot of people not assigned to any team--should we >>>> talk through the list at some point? >>>> >>>> https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dHF4N >>>> lhocFhjeEk4MFJwNUlQS0Y4OEE#gid=2 >>>> >>>> I added Travis Harrison to my tech doc team, > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team

1 0

FW: build team assignments
by Land, Miriam L. 24 Jan '13

24 Jan '13

Release Team, Tom would like to have a conference call on Friday to discuss team assignments. Nomi is only available Fri 9-10am PST (11-12 CST, 12-2 EST). Tom and I are also available at that time. If you have an interest in getting people for your team, please let Tom know of any conflicts. Miriam On 1/24/13 2:17 AM, "Nomi Harris" <nlharris(a)lbl.gov> wrote: >The only time I'm available on Fri is 9-10am PST. Does that work for you? > Nomi > >On Jan 23, 2013, at 11:15 PM, Thomas Brettin <Brettin(a)mcs.anl.gov> wrote: > >> yes, i think we need to have a con-call -- release engineering team -- >>friday -- to refine and adjust. We also need to do something about the >>non-performers. >> >> tom >> >> On Jan 23, 2013, at 11:57 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >> >>> There are still a lot of people not assigned to any team--should we >>>talk through the list at some point? >>> >>>https://docs.google.com/a/lbl.gov/spreadsheet/ccc?key=0Ana5oznWypH2dHF4N >>>lhocFhjeEk4MFJwNUlQS0Y4OEE#gid=2 >>> >>> I added Travis Harrison to my tech doc team,

1 0

Re: [Release-team] Self-cc behavior of [email protected]
by Land, Miriam L. 24 Jan '13

24 Jan '13

Nomi, You can set your personal preferences for each mail list. When you get to main page for the list (e.g., http://lists.kbase.us/mailman/listinfo/kbase-devel) at the very bottom, you enter your email address to change your options and/or password. The button has the words 'Unsubscribe or edit options'. It is below the option to see the list of subscribers. Miriam From: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> Date: Thursday, January 24, 2013 1:27 AM To: Dan Olson <dolson(a)mcs.anl.gov<mailto:[email protected]>> Cc: "release-team(a)lists.kbase.us<mailto:[email protected]>" <release-team(a)lists.kbase.us<mailto:[email protected]>> Subject: [Release-team] Self-cc behavior of release-team(a)lists.kbase.us<mailto:[email protected]> Hi Dan, The release-team mailing list, like all of our mailing lists, seems to default to NOT sending a copy of the message to the sender. I find this endlessly frustrating, as I usually DO want to keep a copy and forget to cc myself. If no one else minds, would it be possible to change the behavior so it DOES send the message back to the sender? Thanks, Nomi

1 0

Re: [Release-team] Oops
by Thomas Brettin 24 Jan '13

24 Jan '13

Not sure, but I do favor sending out targeted messages to the module owners as soon as we have a status. the is most important for those that fail. I'm less concerned with those that pass. Tom On Jan 24, 2013, at 12:31 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > I think maybe I wasn't supposed to send "ok" messages yet to the developers whose API docs were ok? Did I jump the gun on that? > Sorry, > Nomi > > _______________________________________________ > 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

Oops
by Nomi Harris 24 Jan '13

24 Jan '13

I think maybe I wasn't supposed to send "ok" messages yet to the developers whose API docs were ok? Did I jump the gun on that? Sorry, Nomi

1 0

API docs for your module
by Nomi Harris 24 Jan '13

24 Jan '13

Dear KBase Module Owner, Modules are now required to have API docs up at http://140.221.92.231/services/docs/ in order to be included in the release. https://trac.kbase.us/projects/kbase/wiki/TechDocChecking describes the process the Tech Doc team uses to check API docs and other relevant documentation. The key step is: If the module's Makefile conforms to the KBase standard Makefile, “make deploy” will have run “make deploy-docs”, which should make the html documents and copy them to webroot: ($(TARGET)/services/$(SERVICE)/webroot/ where $(TARGET) is typically /kb/deployment and $(SERVICE) is the name of your service--so, for example, /kb/deployment/services/idserver/webroot). These docs are normally generated from the comments in the typespec. If the html API docs are properly made during the deploy, you should be able to see them at http://140.221.92.231/services/docs/SERVICE_NAME. RESULTS OF TECH DOC CHECK (Minor release, week of 1/21/2013) MODULE NAME: kb_model_seed AUTHOR(S): Chris Henry, Scott Devoid DIRECTORY FOR API DOCS: (none) API DOCS PRESENT AT THAT URL? No. (No deploy-docs target in Makefile.) API DOCS OK? No

1 0

API docs for your module
by Nomi Harris 24 Jan '13

24 Jan '13

Dear KBase Module Owner, Modules are now required to have API docs up at http://140.221.92.231/services/docs/ in order to be included in the release. https://trac.kbase.us/projects/kbase/wiki/TechDocChecking describes the process the Tech Doc team uses to check API docs and other relevant documentation. The key step is: If the module's Makefile conforms to the KBase standard Makefile, “make deploy” will have run “make deploy-docs”, which should make the html documents and copy them to webroot: ($(TARGET)/services/$(SERVICE)/webroot/ where $(TARGET) is typically /kb/deployment and $(SERVICE) is the name of your service--so, for example, /kb/deployment/services/idserver/webroot). These docs are normally generated from the comments in the typespec. If the html API docs are properly made during the deploy, you should be able to see them at http://140.221.92.231/services/docs/SERVICE_NAME. RESULTS OF TECH DOC CHECK (Minor release, week of 1/21/2013) MODULE NAME: cluster_service AUTHOR(S): Shreyas DIRECTORY FOR API DOCS: http://140.221.92.231/services/docs/cluster_service API DOCS PRESENT AT THAT URL? yes API DOCS OK? yes

1 0

API docs for your module
by Nomi Harris 24 Jan '13

24 Jan '13

Dear KBase Module Owner, Modules are now required to have API docs up at http://140.221.92.231/services/docs/ in order to be included in the release. https://trac.kbase.us/projects/kbase/wiki/TechDocChecking describes the process the Tech Doc team uses to check API docs and other relevant documentation. The key step is: If the module's Makefile conforms to the KBase standard Makefile, “make deploy” will have run “make deploy-docs”, which should make the html documents and copy them to webroot: ($(TARGET)/services/$(SERVICE)/webroot/ where $(TARGET) is typically /kb/deployment and $(SERVICE) is the name of your service--so, for example, /kb/deployment/services/idserver/webroot). These docs are normally generated from the comments in the typespec. If the html API docs are properly made during the deploy, you should be able to see them at http://140.221.92.231/services/docs/SERVICE_NAME. RESULTS OF TECH DOC CHECK (Minor release, week of 1/21/2013) MODULE NAME: matR AUTHOR(S): Travis DIRECTORY FOR API DOCS: http://140.221.92.231/services/docs/matR API DOCS PRESENT AT THAT URL? No. Not sure why, since Makefile does have a deploy-docs target. API DOCS OK? No

1 0