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

Re: [Release-team] Need API doc updated for workspace
by Erik Pearson 03 Jul '14

03 Jul '14

Dan, Or perhaps we should just make “Perl API” and “Java API” links directly in the Workspace section of the services page? http://kbase.us/developer_zone/services Erik. On Jul 3, 2014, at 10:39 AM, Murphy-Olson, Daniel E. <dolson(a)mcs.anl.gov> wrote: > Erik, > > The java docs are available at http://kbase.us/services/docs/workspace/javadoc/. Maybe we can link to this in the sidebar? > > Dan > ________________________________________ > From: release-team-bounces(a)lists.kbase.us [release-team-bounces(a)lists.kbase.us] on behalf of Erik Pearson [eapearson(a)lbl.gov] > Sent: Thursday, July 03, 2014 12:36 PM > To: release-team(a)lists.kbase.us > Subject: Re: [Release-team] Need API doc updated for workspace > > The workspace docs (Perl API, Release Notes) have been updated on the site to release 0.1.6 of workspace_deluxe. In the docs repo they live in workspace_deluxe, and the (internal include) links now reflect this. This was done from outside the workspace_deluxe repo without touching it other than checking out to 0.1.6. For Java API, command line docs, and maybe other stuff, I would need to build workspace in a dev-container, something I’m not yet familiar with. > > Erik. > > On Jul 2, 2014, at 2:18 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: > >> Thanks, Erik. >> >> I discussed this issue (updating the API docs when needed) with Erik. In the longer term, he will look into automating this. In the short term, he just needs to know when a service has been (re)deployed so he can update the API doc for it. He and I couldn’t think of any way he would know this unless Dan tells him, but if there’s some way he could be automatically informed, please let us know! >> >> Nomi >> >> On Jul 2, 2014, at 12:42 PM, Erik Pearson <eapearson(a)lbl.gov> wrote: >> >>> Okay, so I can either build the docs from the workspace_deluxe repo 0.1.6 release or someone can just send me or point me to the location of the build/deployed docs, in either case I’ll take care of incorporating the workspace docs into the docs repo. >>> >>> Erik. >>> >>> >>> On Jul 2, 2014, at 12:05 PM, Erik Pearson <eapearson(a)lbl.gov> wrote: >>> >>>> On Jul 2, 2014, at 11:46 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: >>>> >>>>> Dear Release Team, >>>>> Gavin informed me that the API doc at http://kbase.us/developer-zone/documentation/workspace-service/ is out of date—it should have been updated when the newer version of the workspace service was deployed to production. >>>>> >>>>> What is the current situation with the updating of these API docs—does it require a human to copy them somewhere, or should that happen automatically when a service is deployed to production? >>>> >>>> This specific doc needs to appear in the docs repo as workspace_service/workspaceService.html. >>>> >>>> There is a magic script which which will separate the navigation and the document body and store them in separate files, which are then included directly into the web page (yes, as includes, so whenever the files change the doc web page just shows the new files.) >>>> >>>> There is a manual step for the API doc — I will notice the commit to the docs repo and do the work. Release notes will be automatically updated since they are read straight from the repo. There is also a related “Command Line Help” document located at docs/command_line_prod/Workspace_Service_CommandLineHelp.txt and will be updated on the site automatically (it is shown simply as a plain text page). >>>> >>>> We have plans to for a documentation build process including detection of changes to source docs. >>>> >>>> Erik. >>>> >>>>> >>>>> Also, please add Erik to the release-team mailing list. He is handling the web-facing part (adding the kbase “style” to the API docs). >>>>> >>>>> Thanks, >>>>> Nomi >>>>> >>>>> Begin forwarded message: >>>>> >>>>>> From: Christopher Henry <chrisshenry(a)gmail.com> >>>>>> Subject: Re: workspace docs on website out of date >>>>>> Date: July 2, 2014 at 11:39:23 AM PDT >>>>>> To: Nomi Harris <nlharris(a)lbl.gov> >>>>>> Cc: Gavin A Price <gavinaprice(a)gmail.com> >>>>>> >>>>>> Yes! >>>>>> >>>>>> On Jul 2, 2014, at 1:36 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >>>>>> >>>>>>> Ok, so you’re saying the API doc at http://kbase.us/developer-zone/documentation/workspace-service/ already should have been updated to 0.1.6? >>>>>>> >>>>>>> On Jul 2, 2014, at 11:34 AM, Gavin A Price <gavinaprice(a)gmail.com> wrote: >>>>>>> >>>>>>>> production has been running 0.1.6 for months. >>>>>>>> >>>>>>>> production is *also* running 0.0.5 but no one should be using that other than Chris for data transfer and job handling purposes. >>>>>>>> >>>>>>>> -g >>>>>>>> >>>>>>>> On 7/2/2014 11:24 AM, Nomi Harris wrote: >>>>>>>>> When the production version updates to 0.1.6 then the API doc should get updated during the deploy process. >>>>>>>>> >>>>>>>>> On Jun 26, 2014, at 4:45 PM, Gavin A Price<gavinaprice(a)gmail.com> wrote: >>>>>>>>> >>>>>>>>>> It's probably because 0.0.5 is still running in production at the workspace and workspace_service endpoints (I think those are right) because the data transfer is still ongoing and FBA still uses the workspace as a job runner. >>>>>>>>>> >>>>>>>>>> 0.1.6 is also running at the ws endpoint, but that's the version everyone should be using at this point. >>>>>>>>>> >>>>>>>>>> -g >>>>>>>>>> >>>>>>>>>> On 6/26/2014 4:39 PM, Nomi Harris wrote: >>>>>>>>>>> When a service is (re)deployed into production, its API doc is supposed to get pushed as well. I’m not sure why that didn’t happen in this case. I will investigate. >>>>>>>>>>> >>>>>>>>>>> On Jun 26, 2014, at 4:37 PM, Gavin A Price<gavinaprice(a)gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> It's been brought to my attention that we're still on version 0.0.5 of the workspace docs here: http://kbase.us/developer-zone/documentation/workspace-service/ >>>>>>>>>>>> >>>>>>>>>>>> Should we update to the 0.1.6 docs, which is currently in production? If so, Nomi, could you explain the process? >>>>>>>>>>>> >>>>>>>>>>>> Thanks, Gavin >>>>>>>>> >>> >>> _______________________________________________ >>> 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] Need API doc updated for workspace
by Murphy-Olson, Daniel E. 03 Jul '14

03 Jul '14

Erik, The java docs are available at http://kbase.us/services/docs/workspace/javadoc/. Maybe we can link to this in the sidebar? Dan ________________________________________ From: release-team-bounces(a)lists.kbase.us [release-team-bounces(a)lists.kbase.us] on behalf of Erik Pearson [eapearson(a)lbl.gov] Sent: Thursday, July 03, 2014 12:36 PM To: release-team(a)lists.kbase.us Subject: Re: [Release-team] Need API doc updated for workspace The workspace docs (Perl API, Release Notes) have been updated on the site to release 0.1.6 of workspace_deluxe. In the docs repo they live in workspace_deluxe, and the (internal include) links now reflect this. This was done from outside the workspace_deluxe repo without touching it other than checking out to 0.1.6. For Java API, command line docs, and maybe other stuff, I would need to build workspace in a dev-container, something I’m not yet familiar with. Erik. On Jul 2, 2014, at 2:18 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: > Thanks, Erik. > > I discussed this issue (updating the API docs when needed) with Erik. In the longer term, he will look into automating this. In the short term, he just needs to know when a service has been (re)deployed so he can update the API doc for it. He and I couldn’t think of any way he would know this unless Dan tells him, but if there’s some way he could be automatically informed, please let us know! > > Nomi > > On Jul 2, 2014, at 12:42 PM, Erik Pearson <eapearson(a)lbl.gov> wrote: > >> Okay, so I can either build the docs from the workspace_deluxe repo 0.1.6 release or someone can just send me or point me to the location of the build/deployed docs, in either case I’ll take care of incorporating the workspace docs into the docs repo. >> >> Erik. >> >> >> On Jul 2, 2014, at 12:05 PM, Erik Pearson <eapearson(a)lbl.gov> wrote: >> >>> On Jul 2, 2014, at 11:46 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: >>> >>>> Dear Release Team, >>>> Gavin informed me that the API doc at http://kbase.us/developer-zone/documentation/workspace-service/ is out of date—it should have been updated when the newer version of the workspace service was deployed to production. >>>> >>>> What is the current situation with the updating of these API docs—does it require a human to copy them somewhere, or should that happen automatically when a service is deployed to production? >>> >>> This specific doc needs to appear in the docs repo as workspace_service/workspaceService.html. >>> >>> There is a magic script which which will separate the navigation and the document body and store them in separate files, which are then included directly into the web page (yes, as includes, so whenever the files change the doc web page just shows the new files.) >>> >>> There is a manual step for the API doc — I will notice the commit to the docs repo and do the work. Release notes will be automatically updated since they are read straight from the repo. There is also a related “Command Line Help” document located at docs/command_line_prod/Workspace_Service_CommandLineHelp.txt and will be updated on the site automatically (it is shown simply as a plain text page). >>> >>> We have plans to for a documentation build process including detection of changes to source docs. >>> >>> Erik. >>> >>>> >>>> Also, please add Erik to the release-team mailing list. He is handling the web-facing part (adding the kbase “style” to the API docs). >>>> >>>> Thanks, >>>> Nomi >>>> >>>> Begin forwarded message: >>>> >>>>> From: Christopher Henry <chrisshenry(a)gmail.com> >>>>> Subject: Re: workspace docs on website out of date >>>>> Date: July 2, 2014 at 11:39:23 AM PDT >>>>> To: Nomi Harris <nlharris(a)lbl.gov> >>>>> Cc: Gavin A Price <gavinaprice(a)gmail.com> >>>>> >>>>> Yes! >>>>> >>>>> On Jul 2, 2014, at 1:36 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >>>>> >>>>>> Ok, so you’re saying the API doc at http://kbase.us/developer-zone/documentation/workspace-service/ already should have been updated to 0.1.6? >>>>>> >>>>>> On Jul 2, 2014, at 11:34 AM, Gavin A Price <gavinaprice(a)gmail.com> wrote: >>>>>> >>>>>>> production has been running 0.1.6 for months. >>>>>>> >>>>>>> production is *also* running 0.0.5 but no one should be using that other than Chris for data transfer and job handling purposes. >>>>>>> >>>>>>> -g >>>>>>> >>>>>>> On 7/2/2014 11:24 AM, Nomi Harris wrote: >>>>>>>> When the production version updates to 0.1.6 then the API doc should get updated during the deploy process. >>>>>>>> >>>>>>>> On Jun 26, 2014, at 4:45 PM, Gavin A Price<gavinaprice(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> It's probably because 0.0.5 is still running in production at the workspace and workspace_service endpoints (I think those are right) because the data transfer is still ongoing and FBA still uses the workspace as a job runner. >>>>>>>>> >>>>>>>>> 0.1.6 is also running at the ws endpoint, but that's the version everyone should be using at this point. >>>>>>>>> >>>>>>>>> -g >>>>>>>>> >>>>>>>>> On 6/26/2014 4:39 PM, Nomi Harris wrote: >>>>>>>>>> When a service is (re)deployed into production, its API doc is supposed to get pushed as well. I’m not sure why that didn’t happen in this case. I will investigate. >>>>>>>>>> >>>>>>>>>> On Jun 26, 2014, at 4:37 PM, Gavin A Price<gavinaprice(a)gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> It's been brought to my attention that we're still on version 0.0.5 of the workspace docs here: http://kbase.us/developer-zone/documentation/workspace-service/ >>>>>>>>>>> >>>>>>>>>>> Should we update to the 0.1.6 docs, which is currently in production? If so, Nomi, could you explain the process? >>>>>>>>>>> >>>>>>>>>>> Thanks, Gavin >>>>>>>> >> >> _______________________________________________ >> 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] Need API doc updated for workspace
by Erik Pearson 03 Jul '14

03 Jul '14

The workspace docs (Perl API, Release Notes) have been updated on the site to release 0.1.6 of workspace_deluxe. In the docs repo they live in workspace_deluxe, and the (internal include) links now reflect this. This was done from outside the workspace_deluxe repo without touching it other than checking out to 0.1.6. For Java API, command line docs, and maybe other stuff, I would need to build workspace in a dev-container, something I’m not yet familiar with. Erik. On Jul 2, 2014, at 2:18 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: > Thanks, Erik. > > I discussed this issue (updating the API docs when needed) with Erik. In the longer term, he will look into automating this. In the short term, he just needs to know when a service has been (re)deployed so he can update the API doc for it. He and I couldn’t think of any way he would know this unless Dan tells him, but if there’s some way he could be automatically informed, please let us know! > > Nomi > > On Jul 2, 2014, at 12:42 PM, Erik Pearson <eapearson(a)lbl.gov> wrote: > >> Okay, so I can either build the docs from the workspace_deluxe repo 0.1.6 release or someone can just send me or point me to the location of the build/deployed docs, in either case I’ll take care of incorporating the workspace docs into the docs repo. >> >> Erik. >> >> >> On Jul 2, 2014, at 12:05 PM, Erik Pearson <eapearson(a)lbl.gov> wrote: >> >>> On Jul 2, 2014, at 11:46 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: >>> >>>> Dear Release Team, >>>> Gavin informed me that the API doc at http://kbase.us/developer-zone/documentation/workspace-service/ is out of date—it should have been updated when the newer version of the workspace service was deployed to production. >>>> >>>> What is the current situation with the updating of these API docs—does it require a human to copy them somewhere, or should that happen automatically when a service is deployed to production? >>> >>> This specific doc needs to appear in the docs repo as workspace_service/workspaceService.html. >>> >>> There is a magic script which which will separate the navigation and the document body and store them in separate files, which are then included directly into the web page (yes, as includes, so whenever the files change the doc web page just shows the new files.) >>> >>> There is a manual step for the API doc — I will notice the commit to the docs repo and do the work. Release notes will be automatically updated since they are read straight from the repo. There is also a related “Command Line Help” document located at docs/command_line_prod/Workspace_Service_CommandLineHelp.txt and will be updated on the site automatically (it is shown simply as a plain text page). >>> >>> We have plans to for a documentation build process including detection of changes to source docs. >>> >>> Erik. >>> >>>> >>>> Also, please add Erik to the release-team mailing list. He is handling the web-facing part (adding the kbase “style” to the API docs). >>>> >>>> Thanks, >>>> Nomi >>>> >>>> Begin forwarded message: >>>> >>>>> From: Christopher Henry <chrisshenry(a)gmail.com> >>>>> Subject: Re: workspace docs on website out of date >>>>> Date: July 2, 2014 at 11:39:23 AM PDT >>>>> To: Nomi Harris <nlharris(a)lbl.gov> >>>>> Cc: Gavin A Price <gavinaprice(a)gmail.com> >>>>> >>>>> Yes! >>>>> >>>>> On Jul 2, 2014, at 1:36 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >>>>> >>>>>> Ok, so you’re saying the API doc at http://kbase.us/developer-zone/documentation/workspace-service/ already should have been updated to 0.1.6? >>>>>> >>>>>> On Jul 2, 2014, at 11:34 AM, Gavin A Price <gavinaprice(a)gmail.com> wrote: >>>>>> >>>>>>> production has been running 0.1.6 for months. >>>>>>> >>>>>>> production is *also* running 0.0.5 but no one should be using that other than Chris for data transfer and job handling purposes. >>>>>>> >>>>>>> -g >>>>>>> >>>>>>> On 7/2/2014 11:24 AM, Nomi Harris wrote: >>>>>>>> When the production version updates to 0.1.6 then the API doc should get updated during the deploy process. >>>>>>>> >>>>>>>> On Jun 26, 2014, at 4:45 PM, Gavin A Price<gavinaprice(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> It's probably because 0.0.5 is still running in production at the workspace and workspace_service endpoints (I think those are right) because the data transfer is still ongoing and FBA still uses the workspace as a job runner. >>>>>>>>> >>>>>>>>> 0.1.6 is also running at the ws endpoint, but that's the version everyone should be using at this point. >>>>>>>>> >>>>>>>>> -g >>>>>>>>> >>>>>>>>> On 6/26/2014 4:39 PM, Nomi Harris wrote: >>>>>>>>>> When a service is (re)deployed into production, its API doc is supposed to get pushed as well. I’m not sure why that didn’t happen in this case. I will investigate. >>>>>>>>>> >>>>>>>>>> On Jun 26, 2014, at 4:37 PM, Gavin A Price<gavinaprice(a)gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> It's been brought to my attention that we're still on version 0.0.5 of the workspace docs here: http://kbase.us/developer-zone/documentation/workspace-service/ >>>>>>>>>>> >>>>>>>>>>> Should we update to the 0.1.6 docs, which is currently in production? If so, Nomi, could you explain the process? >>>>>>>>>>> >>>>>>>>>>> Thanks, Gavin >>>>>>>> >> >> _______________________________________________ >> 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] Need API doc updated for workspace
by Nomi Harris 02 Jul '14

02 Jul '14

Thanks, Erik. I discussed this issue (updating the API docs when needed) with Erik. In the longer term, he will look into automating this. In the short term, he just needs to know when a service has been (re)deployed so he can update the API doc for it. He and I couldn’t think of any way he would know this unless Dan tells him, but if there’s some way he could be automatically informed, please let us know! Nomi On Jul 2, 2014, at 12:42 PM, Erik Pearson <eapearson(a)lbl.gov> wrote: > Okay, so I can either build the docs from the workspace_deluxe repo 0.1.6 release or someone can just send me or point me to the location of the build/deployed docs, in either case I’ll take care of incorporating the workspace docs into the docs repo. > > Erik. > > > On Jul 2, 2014, at 12:05 PM, Erik Pearson <eapearson(a)lbl.gov> wrote: > >> On Jul 2, 2014, at 11:46 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: >> >>> Dear Release Team, >>> Gavin informed me that the API doc at http://kbase.us/developer-zone/documentation/workspace-service/ is out of date—it should have been updated when the newer version of the workspace service was deployed to production. >>> >>> What is the current situation with the updating of these API docs—does it require a human to copy them somewhere, or should that happen automatically when a service is deployed to production? >> >> This specific doc needs to appear in the docs repo as workspace_service/workspaceService.html. >> >> There is a magic script which which will separate the navigation and the document body and store them in separate files, which are then included directly into the web page (yes, as includes, so whenever the files change the doc web page just shows the new files.) >> >> There is a manual step for the API doc — I will notice the commit to the docs repo and do the work. Release notes will be automatically updated since they are read straight from the repo. There is also a related “Command Line Help” document located at docs/command_line_prod/Workspace_Service_CommandLineHelp.txt and will be updated on the site automatically (it is shown simply as a plain text page). >> >> We have plans to for a documentation build process including detection of changes to source docs. >> >> Erik. >> >>> >>> Also, please add Erik to the release-team mailing list. He is handling the web-facing part (adding the kbase “style” to the API docs). >>> >>> Thanks, >>> Nomi >>> >>> Begin forwarded message: >>> >>>> From: Christopher Henry <chrisshenry(a)gmail.com> >>>> Subject: Re: workspace docs on website out of date >>>> Date: July 2, 2014 at 11:39:23 AM PDT >>>> To: Nomi Harris <nlharris(a)lbl.gov> >>>> Cc: Gavin A Price <gavinaprice(a)gmail.com> >>>> >>>> Yes! >>>> >>>> On Jul 2, 2014, at 1:36 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >>>> >>>>> Ok, so you’re saying the API doc at http://kbase.us/developer-zone/documentation/workspace-service/ already should have been updated to 0.1.6? >>>>> >>>>> On Jul 2, 2014, at 11:34 AM, Gavin A Price <gavinaprice(a)gmail.com> wrote: >>>>> >>>>>> production has been running 0.1.6 for months. >>>>>> >>>>>> production is *also* running 0.0.5 but no one should be using that other than Chris for data transfer and job handling purposes. >>>>>> >>>>>> -g >>>>>> >>>>>> On 7/2/2014 11:24 AM, Nomi Harris wrote: >>>>>>> When the production version updates to 0.1.6 then the API doc should get updated during the deploy process. >>>>>>> >>>>>>> On Jun 26, 2014, at 4:45 PM, Gavin A Price<gavinaprice(a)gmail.com> wrote: >>>>>>> >>>>>>>> It's probably because 0.0.5 is still running in production at the workspace and workspace_service endpoints (I think those are right) because the data transfer is still ongoing and FBA still uses the workspace as a job runner. >>>>>>>> >>>>>>>> 0.1.6 is also running at the ws endpoint, but that's the version everyone should be using at this point. >>>>>>>> >>>>>>>> -g >>>>>>>> >>>>>>>> On 6/26/2014 4:39 PM, Nomi Harris wrote: >>>>>>>>> When a service is (re)deployed into production, its API doc is supposed to get pushed as well. I’m not sure why that didn’t happen in this case. I will investigate. >>>>>>>>> >>>>>>>>> On Jun 26, 2014, at 4:37 PM, Gavin A Price<gavinaprice(a)gmail.com> wrote: >>>>>>>>> >>>>>>>>>> It's been brought to my attention that we're still on version 0.0.5 of the workspace docs here: http://kbase.us/developer-zone/documentation/workspace-service/ >>>>>>>>>> >>>>>>>>>> Should we update to the 0.1.6 docs, which is currently in production? If so, Nomi, could you explain the process? >>>>>>>>>> >>>>>>>>>> Thanks, Gavin >>>>>>> > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team

1 0

Re: [Release-team] Need API doc updated for workspace
by Erik Pearson 02 Jul '14

02 Jul '14

Okay, so I can either build the docs from the workspace_deluxe repo 0.1.6 release or someone can just send me or point me to the location of the build/deployed docs, in either case I’ll take care of incorporating the workspace docs into the docs repo. Erik. On Jul 2, 2014, at 12:05 PM, Erik Pearson <eapearson(a)lbl.gov> wrote: > On Jul 2, 2014, at 11:46 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > >> Dear Release Team, >> Gavin informed me that the API doc at http://kbase.us/developer-zone/documentation/workspace-service/ is out of date—it should have been updated when the newer version of the workspace service was deployed to production. >> >> What is the current situation with the updating of these API docs—does it require a human to copy them somewhere, or should that happen automatically when a service is deployed to production? > > This specific doc needs to appear in the docs repo as workspace_service/workspaceService.html. > > There is a magic script which which will separate the navigation and the document body and store them in separate files, which are then included directly into the web page (yes, as includes, so whenever the files change the doc web page just shows the new files.) > > There is a manual step for the API doc — I will notice the commit to the docs repo and do the work. Release notes will be automatically updated since they are read straight from the repo. There is also a related “Command Line Help” document located at docs/command_line_prod/Workspace_Service_CommandLineHelp.txt and will be updated on the site automatically (it is shown simply as a plain text page). > > We have plans to for a documentation build process including detection of changes to source docs. > > Erik. > >> >> Also, please add Erik to the release-team mailing list. He is handling the web-facing part (adding the kbase “style” to the API docs). >> >> Thanks, >> Nomi >> >> Begin forwarded message: >> >>> From: Christopher Henry <chrisshenry(a)gmail.com> >>> Subject: Re: workspace docs on website out of date >>> Date: July 2, 2014 at 11:39:23 AM PDT >>> To: Nomi Harris <nlharris(a)lbl.gov> >>> Cc: Gavin A Price <gavinaprice(a)gmail.com> >>> >>> Yes! >>> >>> On Jul 2, 2014, at 1:36 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >>> >>>> Ok, so you’re saying the API doc at http://kbase.us/developer-zone/documentation/workspace-service/ already should have been updated to 0.1.6? >>>> >>>> On Jul 2, 2014, at 11:34 AM, Gavin A Price <gavinaprice(a)gmail.com> wrote: >>>> >>>>> production has been running 0.1.6 for months. >>>>> >>>>> production is *also* running 0.0.5 but no one should be using that other than Chris for data transfer and job handling purposes. >>>>> >>>>> -g >>>>> >>>>> On 7/2/2014 11:24 AM, Nomi Harris wrote: >>>>>> When the production version updates to 0.1.6 then the API doc should get updated during the deploy process. >>>>>> >>>>>> On Jun 26, 2014, at 4:45 PM, Gavin A Price<gavinaprice(a)gmail.com> wrote: >>>>>> >>>>>>> It's probably because 0.0.5 is still running in production at the workspace and workspace_service endpoints (I think those are right) because the data transfer is still ongoing and FBA still uses the workspace as a job runner. >>>>>>> >>>>>>> 0.1.6 is also running at the ws endpoint, but that's the version everyone should be using at this point. >>>>>>> >>>>>>> -g >>>>>>> >>>>>>> On 6/26/2014 4:39 PM, Nomi Harris wrote: >>>>>>>> When a service is (re)deployed into production, its API doc is supposed to get pushed as well. I’m not sure why that didn’t happen in this case. I will investigate. >>>>>>>> >>>>>>>> On Jun 26, 2014, at 4:37 PM, Gavin A Price<gavinaprice(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> It's been brought to my attention that we're still on version 0.0.5 of the workspace docs here: http://kbase.us/developer-zone/documentation/workspace-service/ >>>>>>>>> >>>>>>>>> Should we update to the 0.1.6 docs, which is currently in production? If so, Nomi, could you explain the process? >>>>>>>>> >>>>>>>>> Thanks, Gavin >>>>>> >>>> >>> >> >

1 0

Re: [Release-team] Need API doc updated for workspace
by Erik Pearson 02 Jul '14

02 Jul '14

On Jul 2, 2014, at 11:46 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > Dear Release Team, > Gavin informed me that the API doc at http://kbase.us/developer-zone/documentation/workspace-service/ is out of date—it should have been updated when the newer version of the workspace service was deployed to production. > > What is the current situation with the updating of these API docs—does it require a human to copy them somewhere, or should that happen automatically when a service is deployed to production? This specific doc needs to appear in the docs repo as workspace_service/workspaceService.html. There is a magic script which which will separate the navigation and the document body and store them in separate files, which are then included directly into the web page (yes, as includes, so whenever the files change the doc web page just shows the new files.) There is a manual step for the API doc — I will notice the commit to the docs repo and do the work. Release notes will be automatically updated since they are read straight from the repo. There is also a related “Command Line Help” document located at docs/command_line_prod/Workspace_Service_CommandLineHelp.txt and will be updated on the site automatically (it is shown simply as a plain text page). We have plans to for a documentation build process including detection of changes to source docs. Erik. > > Also, please add Erik to the release-team mailing list. He is handling the web-facing part (adding the kbase “style” to the API docs). > > Thanks, > Nomi > > Begin forwarded message: > >> From: Christopher Henry <chrisshenry(a)gmail.com> >> Subject: Re: workspace docs on website out of date >> Date: July 2, 2014 at 11:39:23 AM PDT >> To: Nomi Harris <nlharris(a)lbl.gov> >> Cc: Gavin A Price <gavinaprice(a)gmail.com> >> >> Yes! >> >> On Jul 2, 2014, at 1:36 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >> >>> Ok, so you’re saying the API doc at http://kbase.us/developer-zone/documentation/workspace-service/ already should have been updated to 0.1.6? >>> >>> On Jul 2, 2014, at 11:34 AM, Gavin A Price <gavinaprice(a)gmail.com> wrote: >>> >>>> production has been running 0.1.6 for months. >>>> >>>> production is *also* running 0.0.5 but no one should be using that other than Chris for data transfer and job handling purposes. >>>> >>>> -g >>>> >>>> On 7/2/2014 11:24 AM, Nomi Harris wrote: >>>>> When the production version updates to 0.1.6 then the API doc should get updated during the deploy process. >>>>> >>>>> On Jun 26, 2014, at 4:45 PM, Gavin A Price<gavinaprice(a)gmail.com> wrote: >>>>> >>>>>> It's probably because 0.0.5 is still running in production at the workspace and workspace_service endpoints (I think those are right) because the data transfer is still ongoing and FBA still uses the workspace as a job runner. >>>>>> >>>>>> 0.1.6 is also running at the ws endpoint, but that's the version everyone should be using at this point. >>>>>> >>>>>> -g >>>>>> >>>>>> On 6/26/2014 4:39 PM, Nomi Harris wrote: >>>>>>> When a service is (re)deployed into production, its API doc is supposed to get pushed as well. I’m not sure why that didn’t happen in this case. I will investigate. >>>>>>> >>>>>>> On Jun 26, 2014, at 4:37 PM, Gavin A Price<gavinaprice(a)gmail.com> wrote: >>>>>>> >>>>>>>> It's been brought to my attention that we're still on version 0.0.5 of the workspace docs here: http://kbase.us/developer-zone/documentation/workspace-service/ >>>>>>>> >>>>>>>> Should we update to the 0.1.6 docs, which is currently in production? If so, Nomi, could you explain the process? >>>>>>>> >>>>>>>> Thanks, Gavin >>>>> >>> >> >

1 0

Need API doc updated for workspace
by Nomi Harris 02 Jul '14

02 Jul '14

Dear Release Team, Gavin informed me that the API doc at http://kbase.us/developer-zone/documentation/workspace-service/ is out of date—it should have been updated when the newer version of the workspace service was deployed to production. What is the current situation with the updating of these API docs—does it require a human to copy them somewhere, or should that happen automatically when a service is deployed to production? Also, please add Erik to the release-team mailing list. He is handling the web-facing part (adding the kbase “style” to the API docs). Thanks, Nomi Begin forwarded message: > From: Christopher Henry <chrisshenry(a)gmail.com> > Subject: Re: workspace docs on website out of date > Date: July 2, 2014 at 11:39:23 AM PDT > To: Nomi Harris <nlharris(a)lbl.gov> > Cc: Gavin A Price <gavinaprice(a)gmail.com> > > Yes! > > On Jul 2, 2014, at 1:36 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: > >> Ok, so you’re saying the API doc at http://kbase.us/developer-zone/documentation/workspace-service/ already should have been updated to 0.1.6? >> >> On Jul 2, 2014, at 11:34 AM, Gavin A Price <gavinaprice(a)gmail.com> wrote: >> >>> production has been running 0.1.6 for months. >>> >>> production is *also* running 0.0.5 but no one should be using that other than Chris for data transfer and job handling purposes. >>> >>> -g >>> >>> On 7/2/2014 11:24 AM, Nomi Harris wrote: >>>> When the production version updates to 0.1.6 then the API doc should get updated during the deploy process. >>>> >>>> On Jun 26, 2014, at 4:45 PM, Gavin A Price<gavinaprice(a)gmail.com> wrote: >>>> >>>>> It's probably because 0.0.5 is still running in production at the workspace and workspace_service endpoints (I think those are right) because the data transfer is still ongoing and FBA still uses the workspace as a job runner. >>>>> >>>>> 0.1.6 is also running at the ws endpoint, but that's the version everyone should be using at this point. >>>>> >>>>> -g >>>>> >>>>> On 6/26/2014 4:39 PM, Nomi Harris wrote: >>>>>> When a service is (re)deployed into production, its API doc is supposed to get pushed as well. I’m not sure why that didn’t happen in this case. I will investigate. >>>>>> >>>>>> On Jun 26, 2014, at 4:37 PM, Gavin A Price<gavinaprice(a)gmail.com> wrote: >>>>>> >>>>>>> It's been brought to my attention that we're still on version 0.0.5 of the workspace docs here: http://kbase.us/developer-zone/documentation/workspace-service/ >>>>>>> >>>>>>> Should we update to the 0.1.6 docs, which is currently in production? If so, Nomi, could you explain the process? >>>>>>> >>>>>>> Thanks, Gavin >>>> >> >

1 0