can we talk? On Jun 7, 2013, at 12:37 PM, Nomi Harris <[email protected]> wrote:

On Jun 7, 2013, at 6:36 AM, Thomas Brettin <[email protected]> wrote:

...

analysis_book - not in the release - it's the ipython notebook that Folker did and its a MGRast product.

It's still unclear what the release process is for Labs, but ok, we won't worry about this one for this release.

...

aux_store, not in the release as far as I know because the public can't really touch it.

Right, yes, I should have marked that as internal only.

...

registry - not in the release, it's an internal experimental module

I put that one in parens for that reason.

...

search - has api docs, just not in standard form. just ask guru where the url is

Is search a service as well as a Lab? In either case, it should deploy API docs to the standard location. We shouldn't have to ask the developers where they've put their API docs. (If it's just a Lab and not a service, then the standards are less clear.)

...

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.

Wait, so, if they haven't really changed, what does it mean for them to be "in this release"? If we're releasing them, then that's because they've changed, right? So the developers should be able to tell us how they've changed, if they want their modules to be included in this release.

can we talk?

Nomi

...

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