I would just do a foreach repo, show me the git logs, or number of commits, or something. Many haven't really changed significantly. Based on a 15-30 minutes of detective work, i'd formulate a plan forward. analysis_book - not in the release - it's the ipython notebook that Folker did and its a MGRast product. aux_store, not in the release as far as I know because the public can't really touch it. registry - not in the release, it's an internal experimental module search - has api docs, just not in standard form. just ask guru where the url is On Jun 6, 2013, at 11:17 PM, Nomi Harris <[email protected]> wrote:

A few of the services have up-to-date release notes (and appropriately deployed API docs): auth jnomics protein_info_service translation trees (? -- release notes updated 4/4)

However, many do not have updated release notes and thus are not ready to be included in this release. (Some also don't have API docs in the expected location.) analysis_book assembly auth_service aux_store cluster_service communities_api communities_qc (erdb_service--internal only, right?) experiment feature_selection (also missing api docs) (file_type_service) genotype_phenotype_api kb_seed KBaseFBAModeling (also missing api docs) matR networks ontology_service phispy plant_expression_service (registry) search (also missing api docs) workspace_service

What's the best way to get the missing release notes so we can finish up this release? Do Mike and I need to phone the relevant developers?

Nomi _______________________________________________ Release-team mailing list [email protected] https://lists.kbase.us/mailman/listinfo/release-team