Changing a published item

Anyone signed in can change a published item: Propose a change on its page starts a draft from the version shown, with all its files. The scope, name and type stay the item's.

Everything else works as for a new item: edit, submit, review. Reviewers see what it changes against that version. Several proposals can be open for one item at once.

A proposal can also come from where you made the edit: after you change an installed item in your AI tool, rmk export sends it as a proposal to the version you installed.

If a newer version comes out while a proposal is open, the proposal is stale: approving it would undo what the newer version changed. It can't be approved or released until its author rebases it.

Rebase moves it onto the newest version, file by file:

• files only the proposal changed keep the proposal's changes;
• files only the newer version changed take the newer version's;
• files both changed keep the proposal's, and are listed as conflicts to compare, fix and mark resolved. Submitting waits until none is left.

A proposal that was under review or approved goes back to its author to be reviewed again.

Once approved, it's released like any other submission, as the item's next version. The publish dialog suggests patch, minor or major from what changed (see Patch, minor or major), and the publisher can pick another. Several can go at once; two proposals for the same item can't both go out, since the first makes the other stale.