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

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

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: registry AUTHOR(S): Tom DIRECTORY FOR API DOCS: http://140.221.92.231/services/docs/registry API DOCS PRESENT AT THAT URL? No--directory does not exist, though Makefile does have deploy-docs target. API DOCS OK? No. No API docs at URL. Typespec seems to be reasonably well-commented, though lacking a top-level description.

1 0

Self-cc behavior of [email protected]
by Nomi Harris 24 Jan '13

24 Jan '13

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

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: KBaseFBAModeling AUTHOR(S): Chris H., Matt DeJongh DIRECTORY FOR API DOCS: http://140.221.92.231/services/docs/KBaseFBAModeling 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: typecomp AUTHOR(S): Bob Olson DIRECTORY FOR API DOCS: (none) API DOCS PRESENT AT THAT URL? No API DOCS OK? No API docs--but typecomp doesn't have an API, does it? So I guess it's ok?

1 0