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

new worksheet for this weeks release
by Thomas Brettin 27 Jan '13

27 Jan '13

I created a new worksheet as agreed during our call on Friday. It's the "Jan 28 2013 Minor" tab. Take a look. We can add more as needed. Tom Thomas Brettin 865-603-7760 (cell) brettin(a)mcs.anl.gov

1 0

Re: [Release-team] Are minor releases cumulative? [was Re: Redeploy testing summary]
by Thomas Brettin 27 Jan '13

27 Jan '13

Can we talk by phone? Email isn't working. Tom On Jan 27, 2013, at 12:29 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: > > On Jan 27, 2013, at 6:51 AM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > >> >> On Jan 26, 2013, at 4:42 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: >> >>> Thanks, Miriam. >>> Are minor releases cumulative? In other words, if we released a service last week (say, Ontology), is it included in this minor release as well? I'm guessing not, because there might have been new changes to the service that broke it. >> >> >> A module owner can have their module in the release cycle each week if they choose. I'm targeting that goal. >> >>> That means that I need to move the "Available Now" releases on http://www.kbase.us/developer-zone/services/ back to "Coming Soon", right? >>> If so, then I think we also need to list the services included in each dmg on the Downloads page (http://www.kbase.us/developer-zone/downloads/) >> >> Can someone think of how to auto-generate this? > > Although I'm pro-automation in many cases, this isn't one of them. The amount of effort required to automate this would exceed the (minor) amount of work it takes a human to make these adjustments for each release. > > But you didn't answer the questions: should I make the changes described? > There must be something that I am missing. I don't understand why this change is necessary, so I can't answer the question. I'm available to talk right now. If it has already been released, why would it be changed to coming soon? >>> because a new user might really want one of the services in the first Jan release and thus might want to download the older release instead of the newer one. But what if they want some of the services from the first minor release and some from the second? Is there any way to get both, or do they just have to wait a month for the full release? >> >> This is going to require some thought. The distinction between minor and major releases and how fine the versioning of all the independent parts should be thought through. Also, it needs lend itself to automation or our releases won't scale. Lets put this on the agenda for discussion at the Feb 4 release week. > > Fine, but I still need to know what to do for THIS release. Or are we not making this a release? Are we just waiting until the Feb 4 major build? I need to know that today, too. For this release, I would like to see updates to the dmg with the items that weren't released in the dmg last week and the javascript libraries should be released as well. > > Nomi > >> >> >>> Nomi >>> >>> On Jan 26, 2013, at 7:09 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: >>> >>>> Release team, >>>> >>>> The list of modules that passed testing on either the 1st or redeploy and passed documents are: >>>> >>>> * communities_qc >>>> * erdb_service (private) >>>> * kb_seed >>>> * workspace_service >>>> * And the dependencies idserver, typecomp, cluster_service, kb_model_seed >>>> >>>> Just for completeness, the services that followed our procedure and failed are: >>>> >>>> * genome_annotation – failed make test on redeploy. It may work but until someone rewrites the tests, it fails the established procedure. >>>> * KBaseFBAModeling – failed make test on redeploy >>>> * matR – instructions for running demo (instead of make test) failed on redeploy >>>> * Translation – failed make test on redeploy >>>> * The dependency sim_service still is marked as having no documents but was in the last release. Therefore, it fails the established procedure. >>>> >>>> Miriam > Thomas Brettin 865-603-7760 (cell) brettin(a)mcs.anl.gov

1 0

Re: [Release-team] Are minor releases cumulative? [was Re: Redeploy testing summary]
by Nomi Harris 27 Jan '13

27 Jan '13

On Jan 27, 2013, at 6:51 AM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > > On Jan 26, 2013, at 4:42 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: > >> Thanks, Miriam. >> Are minor releases cumulative? In other words, if we released a service last week (say, Ontology), is it included in this minor release as well? I'm guessing not, because there might have been new changes to the service that broke it. > > > A module owner can have their module in the release cycle each week if they choose. I'm targeting that goal. > >> That means that I need to move the "Available Now" releases on http://www.kbase.us/developer-zone/services/ back to "Coming Soon", right? >> If so, then I think we also need to list the services included in each dmg on the Downloads page (http://www.kbase.us/developer-zone/downloads/) > > Can someone think of how to auto-generate this? Although I'm pro-automation in many cases, this isn't one of them. The amount of effort required to automate this would exceed the (minor) amount of work it takes a human to make these adjustments for each release. But you didn't answer the questions: should I make the changes described? >> because a new user might really want one of the services in the first Jan release and thus might want to download the older release instead of the newer one. But what if they want some of the services from the first minor release and some from the second? Is there any way to get both, or do they just have to wait a month for the full release? > > This is going to require some thought. The distinction between minor and major releases and how fine the versioning of all the independent parts should be thought through. Also, it needs lend itself to automation or our releases won't scale. Lets put this on the agenda for discussion at the Feb 4 release week. Fine, but I still need to know what to do for THIS release. Or are we not making this a release? Are we just waiting until the Feb 4 major build? I need to know that today, too. Nomi > > >> Nomi >> >> On Jan 26, 2013, at 7:09 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: >> >>> Release team, >>> >>> The list of modules that passed testing on either the 1st or redeploy and passed documents are: >>> >>> * communities_qc >>> * erdb_service (private) >>> * kb_seed >>> * workspace_service >>> * And the dependencies idserver, typecomp, cluster_service, kb_model_seed >>> >>> Just for completeness, the services that followed our procedure and failed are: >>> >>> * genome_annotation – failed make test on redeploy. It may work but until someone rewrites the tests, it fails the established procedure. >>> * KBaseFBAModeling – failed make test on redeploy >>> * matR – instructions for running demo (instead of make test) failed on redeploy >>> * Translation – failed make test on redeploy >>> * The dependency sim_service still is marked as having no documents but was in the last release. Therefore, it fails the established procedure. >>> >>> Miriam

1 0

Final: release targets for Jan 28.
by Thomas Brettin 27 Jan '13

27 Jan '13

OK. I just added those services that failed last week based on the email Miriam sent on Saturday. here is the final list for tomorrow. > phi spy > plant_expression_service > genotype_phenotype_api > protein_info_service > prom_service > registry > genome_annotation – failed make test on redeploy. It may work but until someone rewrites the tests, it fails the established procedure. > KBaseFBAModeling – failed make test on redeploy > matR – instructions for running demo (instead of make test) failed on redeploy > translation – failed make test on redeploy > sim_service - still is marked as having no documents but was in the last release. Therefore, it fails the established procedure. On Jan 25, 2013, at 4:05 PM, Thomas Brettin <brettin(a)mcs.anl.gov> wrote: > Here are the targets thus far for the next release. We should add to it > > phi spy > plant_expression_service > genotype_phenotype_api > protein_info_service > prom_service > registry > > > > > > > Thomas Brettin > 865-603-7760 (cell) > brettin(a)mcs.anl.gov > > > Thomas Brettin 865-603-7760 (cell) brettin(a)mcs.anl.gov

1 0

Re: [Release-team] Are minor releases cumulative? [was Re: Redeploy testing summary]
by Thomas Brettin 27 Jan '13

27 Jan '13

On Jan 26, 2013, at 4:42 PM, Nomi Harris <nlharris(a)lbl.gov> wrote: > Thanks, Miriam. > Are minor releases cumulative? In other words, if we released a service last week (say, Ontology), is it included in this minor release as well? I'm guessing not, because there might have been new changes to the service that broke it. A module owner can have their module in the release cycle each week if they choose. I'm targeting that goal. > That means that I need to move the "Available Now" releases on http://www.kbase.us/developer-zone/services/ back to "Coming Soon", right? > If so, then I think we also need to list the services included in each dmg on the Downloads page (http://www.kbase.us/developer-zone/downloads/) Can someone think of how to auto-generate this? > because a new user might really want one of the services in the first Jan release and thus might want to download the older release instead of the newer one. But what if they want some of the services from the first minor release and some from the second? Is there any way to get both, or do they just have to wait a month for the full release? This is going to require some thought. The distinction between minor and major releases and how fine the versioning of all the independent parts should be thought through. Also, it needs lend itself to automation or our releases won't scale. Lets put this on the agenda for discussion at the Feb 4 release week. > Nomi > > On Jan 26, 2013, at 7:09 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: > >> Release team, >> >> The list of modules that passed testing on either the 1st or redeploy and passed documents are: >> >> * communities_qc >> * erdb_service (private) >> * kb_seed >> * workspace_service >> * And the dependencies idserver, typecomp, cluster_service, kb_model_seed >> >> Just for completeness, the services that followed our procedure and failed are: >> >> * genome_annotation – failed make test on redeploy. It may work but until someone rewrites the tests, it fails the established procedure. >> * KBaseFBAModeling – failed make test on redeploy >> * matR – instructions for running demo (instead of make test) failed on redeploy >> * Translation – failed make test on redeploy >> * The dependency sim_service still is marked as having no documents but was in the last release. Therefore, it fails the established procedure. >> >> Miriam >> _______________________________________________ >> 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

Are minor releases cumulative? [was Re: Redeploy testing summary]
by Nomi Harris 26 Jan '13

26 Jan '13

Thanks, Miriam. Are minor releases cumulative? In other words, if we released a service last week (say, Ontology), is it included in this minor release as well? I'm guessing not, because there might have been new changes to the service that broke it. That means that I need to move the "Available Now" releases on http://www.kbase.us/developer-zone/services/ back to "Coming Soon", right? If so, then I think we also need to list the services included in each dmg on the Downloads page (http://www.kbase.us/developer-zone/downloads/) because a new user might really want one of the services in the first Jan release and thus might want to download the older release instead of the newer one. But what if they want some of the services from the first minor release and some from the second? Is there any way to get both, or do they just have to wait a month for the full release? Nomi On Jan 26, 2013, at 7:09 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: > Release team, > > The list of modules that passed testing on either the 1st or redeploy and passed documents are: > > * communities_qc > * erdb_service (private) > * kb_seed > * workspace_service > * And the dependencies idserver, typecomp, cluster_service, kb_model_seed > > Just for completeness, the services that followed our procedure and failed are: > > * genome_annotation – failed make test on redeploy. It may work but until someone rewrites the tests, it fails the established procedure. > * KBaseFBAModeling – failed make test on redeploy > * matR – instructions for running demo (instead of make test) failed on redeploy > * Translation – failed make test on redeploy > * The dependency sim_service still is marked as having no documents but was in the last release. Therefore, it fails the established procedure. > > Miriam > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team

1 0

Redeploy testing summary
by Land, Miriam L. 26 Jan '13

26 Jan '13

Release team, The list of modules that passed testing on either the 1st or redeploy and passed documents are: * communities_qc * erdb_service (private) * kb_seed * workspace_service * And the dependencies idserver, typecomp, cluster_service, kb_model_seed Just for completeness, the services that followed our procedure and failed are: * genome_annotation – failed make test on redeploy. It may work but until someone rewrites the tests, it fails the established procedure. * KBaseFBAModeling – failed make test on redeploy * matR – instructions for running demo (instead of make test) failed on redeploy * Translation – failed make test on redeploy * The dependency sim_service still is marked as having no documents but was in the last release. Therefore, it fails the established procedure. Miriam

1 0

release targets for Jan 28.
by Thomas Brettin 25 Jan '13

25 Jan '13

Here are the targets thus far for the next release. We should add to it phi spy plant_expression_service genotype_phenotype_api protein_info_service prom_service registry Thomas Brettin 865-603-7760 (cell) brettin(a)mcs.anl.gov

1 0

Re: [Release-team] Request to share KBase Services
by Thomas Brettin 25 Jan '13

25 Jan '13

who does he belong to? Also, nomi can you change the owner of that spreadsheet back to me, or include me so I see these requests. Thanks, Tom On Jan 25, 2013, at 10:11 AM, Nomi Harris <nlharris(a)lbl.gov> wrote: > Matthew Benedict is, as far as I know, a non-KBase person who has subscribed to the devel mailing list. He now wants access to the KBase Services mailing list. I am not inclined to grant this, unless any of you feel strongly that I should. > Nomi > > Begin forwarded message: > >> From: "Matthew Benedict (Google Drive)" <matthew.n.benedict(a)gmail.com> >> Subject: Request to share KBase Services >> Date: January 25, 2013 7:24:16 AM PST >> To: nlharris(a)lbl.gov >> >> Request to share >> KBase Services >> >> You are the owner of this item and matthew.n.benedict(a)gmail.com has asked that you share this item with: >> + matthew.n.benedict(a)gmail.com >> Add these people in Sharing settings. >> >> Google Drive: create, share, and keep all your stuff in one place. > > _______________________________________________ > 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] redeployment is complete.
by Thomas Brettin 25 Jan '13

25 Jan '13

Would it be helpful to indicate which modules were redeployed, or is everyone now tuned into the kbase services spreadsheet tab Jan 21 Minor? Tom On Jan 25, 2013, at 9:49 AM, Dan Olson <dolson(a)mcs.anl.gov> wrote: > > > ---- > Daniel Murphy-Olson > Systems Administrator > Mathematics & Computer Science Division > Argonne National Laboratory > 630-252-0055 > > _______________________________________________ > 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