On Jan 27, 2013, at 6:51 AM, Thomas Brettin <[email protected]> wrote:

On Jan 26, 2013, at 4:42 PM, Nomi Harris <[email protected]> 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." <[email protected]> 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