Schema change doc needs moving and updating for breaking builds

[mtbcarroll]

http://www.openmicroscopy.org/site/support/omero5/developers/schema-changes.html should discuss the GH breaking label and corresponding CI jobs: how to mark one's PRs and what happens about review. Or, it should reference some other page that explains the process, as I guess it is not only schema changes that make a PR a breaking one.

[sbesson]

My immediate with regard to the ticket description is why is this page under the OMERO developer documentation. Two obvious problems I can spot:

• the link you posted is for the OMERO 5.0.x documentation and there are no model changes in this series
• none of our internal GH/CI cuisine truly belongs ther (esp labels/jobs which do not apply for the 5.0.x series)

Unless someone argues, my preference would be to move this particular page to the Contributing documentation and link the corresponding bits to the relevant section of continuous integration page.

[mtbcarroll]

Sounds good to me. Though, although the current CI page lists the breaking jobs, probably more needs to be said somewhere about the idea and intended workflow behind them.

[hflynn]

@sbesson is right, this stuff belongs in the contributing docs not the OMERO developer docs. I'll edit the ticket name.

[sbesson]

Opened ​https://github.com/openmicroscopy/ome-documentation/pull/699 which reorganizes the CI section of the contributing documentation and includes a more thorough description of the breaking workflow (labels, goals, jobs). This should provide placeholders for moving/referencing the model and schema changes.

[mtbcarroll]

Further to-do's:

1. Explain if it's okay if integration-broken jobs aren't green.
2. Breaking upgrade: Job description should mention it does both from-previous-patch and from-previous-version, and the last section of the schema changes page should mention how one needs to actually provide both scripts.

[sbesson]

See ​https://github.com/openmicroscopy/ome-documentation/pull/704