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

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: sim_service AUTHOR(S): Bob Olson DIRECTORY FOR API DOCS: http://140.221.92.231/services/docs/sim_service API DOCS PRESENT AT THAT URL? No--docs not deployed. (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: kb_seed AUTHOR(S): Bob Olson DIRECTORY FOR API DOCS: http://140.221.92.231/services/docs/cdmi_api 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: kb_seed AUTHOR(S): Bob Olson DIRECTORY FOR API DOCS: http://140.221.92.231/services/docs/cdmi_api 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: genome_annotation AUTHOR(S): Bob Olson DIRECTORY FOR API DOCS: http://140.221.92.231/services/docs/genome_annotation API DOCS PRESENT AT THAT URL? yes API DOCS OK? yes (though missing top-level description)

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: erdb_service AUTHOR(S): Gavin, Keith DIRECTORY FOR API DOCS: http://140.221.92.231/services/docs/erdb_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: communities_qc AUTHOR(S): Andreas, Tobias DIRECTORY FOR API DOCS: http://140.221.92.231/services/docs/communities_qc API DOCS PRESENT AT THAT URL? yes API DOCS OK? yes

1 0

Minor Release Punch List
by Land, Miriam L. 23 Jan '13

23 Jan '13

FYI – I haven't seen any Xs in the Punch List for steps 0 and 1. I believe that the item labeled 1.g. should also send email to Nomi so she can start the documentation review. Miriam

1 0

delay in release start
by Dan Olson 22 Jan '13

22 Jan '13

I'm delayed in starting the release this morning. I hope to start in about 30 minutes. ---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055

1 0

kbase release delay
by Dan Olson 21 Jan '13

21 Jan '13

Hi all, We need to delay the release because of the hardware issues we experienced over the weekend. I expect the issues to be resolved today, and we can start the release tomorrow morning at the same 8am start time. ---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055

1 0

Re: [Release-team] list of modules for release week of Jan 21.
by Thomas Brettin 18 Jan '13

18 Jan '13

We'll pull in the module dependancies if they are listed in the DEPENDENCIES file. Tom On Jan 18, 2013, at 12:35 PM, Matt DeJongh <dejongh(a)hope.edu> wrote: > KBaseFBAModeling depends on the following modules not in the list: > > cluster_service > idserver > typecomp > auth > kb_model_seed > > Should these be included in the list (along with their owners)? > > Matt > > > On Fri, Jan 18, 2013 at 12:00 PM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > > > Module Module Owner Email Address Git Module > > communities_qc Andreas, Tobi Andreas Wilke <wilke(a)mcs.anl.gov> communities_qc > erdb_service Gavin, Keith Gavin A Price <gavinaprice(a)gmail.com> erdb_service > genome_annotation Bob Olson Robert Olson <olson(a)mcs.anl.gov> genome_annotation > kb_seed Bob Olson Robert Olson <olson(a)mcs.anl.gov> kb_seed > KBaseFBAModeling Chris Henry, Matt DeJongh Chris Henry <chrisshenry(a)gmail.com>, Matt DeJongh <dejongh(a)hope.edu> KBaseFBAModeling > matR Travis Travis Harrison <teharrison(a)anl.gov>, Andreas Wilke <wilke(a)mcs.anl.gov> matR > sim_service Bob Olson Robert Olson <olson(a)mcs.anl.gov> sim_service > translation Keith Keller, MIke Sneddon Keith Keller <kkeller(a)lbl.gov>, Michael Sneddon <mwsneddon(a)lbl.gov> translation > workspace_service Chris Henry, Matt DeJongh Chris Henry <chrisshenry(a)gmail.com>, Matt DeJongh <dejongh(a)hope.edu> workspace_service > > > > Thomas Brettin > 865-603-7760 (cell) > brettin(a)mcs.anl.gov > > > > > > > -- > Matt DeJongh, Ph.D. > Computer Science Department > Hope College, Holland, MI 49423 > (616) 395-7429 Thomas Brettin 865-603-7760 (cell) brettin(a)mcs.anl.gov

1 0