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." <[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 _______________________________________________ Release-team mailing list [email protected] https://lists.kbase.us/mailman/listinfo/release-team