Prepare for release of Orizaba

[magnusbaeck]

Applicable Issues

Fixes #356

Description of the Change

Following the release process we claim the new edition in versioning.md and insert references to the new edition in the version history tables of the most recent version of each event type. Also, new for this edition, event_manifest.yml is updated.

Alternate Designs

None.

Benefits

Makes new event versions widely available.

Possible Drawbacks

None.

Sign-off

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

(c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Signed-off-by: Magnus Bäck <magnus.back@axis.com>

[magnusbaeck]

Note that the CI is expected to fail since the edition-orizaba tag is missing. I've run make and tox locally with a local edition-orizaba tag and everything checks out.

[m-linner-ericsson]

Note that the CI is expected to fail since the edition-orizaba tag is missing. I've run make and tox locally with a local edition-orizaba tag and everything checks out.

@magnusbaeck Do we have this documented anywhere or a ticket to fix it?

[magnusbaeck]

Do we have this documented anywhere or a ticket to fix it?

There's no obvious fix for it, but it's documented in https://github.com/eiffel-community/eiffel/blob/master/releases-and-milestones/release-process.md: "Unfortunately, this means that CI for the resulting commit won't succeed until the tag has been created (see next step)."

[m-linner-ericsson]

Do we have this documented anywhere or a ticket to fix it?

There's no obvious fix for it, but it's documented in https://github.com/eiffel-community/eiffel/blob/master/releases-and-milestones/release-process.md: "Unfortunately, this means that CI for the resulting commit won't succeed until the tag has been created (see next step)."

Ok, then we have it documented at least.