Working on the Next Release

draft

Process of working on the next release

A model with life cycle state draft is inputted at Start in the process, and upon completion of the process (End) the model version has the state accepted.

Make changes

Any changes are made and committed and pushed to the draft branch.

For learning more about how to develop the information model, see: TODO.

Propose changes

When changes are finished, they should be proposed to become accepted for the next release.

To achieve this, a pull request is created – if this was not already done – so a review can be carried out by peers.

Review changes

At least one other modeler must review the changes made, and submit whether they accept or reject these changes.

• If the changes are accepted, follow the Accept changes step.
• If the changes are rejected, return to the Make changes step.

Accept changes

If the changes are accepted, the draft branch should be merged onto the main branch, thereby effectuating accepted changes.

In case the resulting version on the main branch is desired to be released, please consult the Releasing a version process.