Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare for release of Lyon #277

Merged
merged 1 commit into from
Oct 12, 2021

Conversation

magnusbaeck
Copy link
Member

Applicable Issues

Fixes #272

Description of the Change

Like what was done for the release of the Paris edition (commit d8fd110) we do two things in preparation of the release of the Lyon edition:

  • Replace all "Current version" references in the Version History tables in the eiffel-vocabulary files with a reference to the (not yet existing) edition-lyon tag.
  • Claim the Lyon edition in the table in versioning.md.

Alternate Designs

None.

Benefits

Makes new protocol 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 magnusbaeck requested a review from a team September 28, 2021 15:20
t-persson
t-persson previously approved these changes Sep 30, 2021
@e-backmark-ericsson
Copy link
Member

Should we set the milestone "Edition Lyon" on this PR as well? I'm not familiar with how milestones work in GitHub.

@magnusbaeck
Copy link
Member Author

Milestones are just containers of issues and PRs so it depends on how we want to use the milestones. So far the Lyon milestone has only contained issues and no PRs so to stick with that ad hoc convention we should leave this PR out (but add the #272 issue).

| 3.2.0 | Current version | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 3.1.0 | Current version | Add `data.persistentLogs.{mediaType,tags}`. |
| 3.2.0 | [edition-lyon](../../../tree/edition-lyon) | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 3.1.0 | [edition-lyon](../../../tree/edition-lyon) | Add `data.persistentLogs.{mediaType,tags}`. |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we really say that 3.1.0 was introduced in edition-lyon? Or should we instead just have a commit id here as it is done for 2.0.0? As edition Lyon contains 3.2.0.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| 3.1.0 | [edition-lyon](../../../tree/edition-lyon) | Add `data.persistentLogs.{mediaType,tags}`. |
| 3.1.0 | No edition set | Add `data.persistentLogs.{mediaType,tags}`. |

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Emil and I talked about this and it's not clear what the Version history table is supposed to convey. Listing both 3.1.0 and 3.2.0 (as in this example) as introduced in Lyon is reasonable in the sense that the changes in both versions were first introduced in the Lyon edition, but if we interpret the table as something that focuses on the event versions it's only 3.2.0 that was introduced in Lyon. 3.1.0 is an "orphan" version that nobody is expected to be using (although it's technically fine to use it).

I'm fine with just about anything right now but I'd like us to figure out something that makes sense and (post-Lyon) align all the Version history tables accordingly.

| 4.2.0 | Current version | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 4.1.0 | Current version | Add `data.liveLogs.{mediaType,tags}`. |
| 4.2.0 | [edition-lyon](../../../tree/edition-lyon) | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 4.1.0 | [edition-lyon](../../../tree/edition-lyon) | Add `data.liveLogs.{mediaType,tags}`. |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as for ActF

| 3.2.0 | Current version | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 3.1.0 | Current version | Added RUNTIME_ENVIRONMENT link type. |
| 3.2.0 | [edition-lyon](../../../tree/edition-lyon) | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 3.1.0 | [edition-lyon](../../../tree/edition-lyon) | Added RUNTIME_ENVIRONMENT link type. |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as for ActF

| 3.2.0 | Current version | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 3.1.0 | Current version | Add `data.persistentLogs.{mediaType,tags}`. |
| 3.2.0 | [edition-lyon](../../../tree/edition-lyon) | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 3.1.0 | [edition-lyon](../../../tree/edition-lyon) | Add `data.persistentLogs.{mediaType,tags}`. |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as for ActF

| 3.2.0 | Current version | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 3.1.0 | Current version | Add `data.liveLogs.{mediaType,tags}`. |
| 3.2.0 | [edition-lyon](../../../tree/edition-lyon) | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 3.1.0 | [edition-lyon](../../../tree/edition-lyon) | Add `data.liveLogs.{mediaType,tags}`. |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as for ActF

| 4.1.1 | Current version | Add missing validation pattern to links.target member (see [Issue 271](https://github.com/eiffel-community/eiffel/issues/271)). |
| 4.1.0 | Current version | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 4.1.1 | [edition-lyon](../../../tree/edition-lyon) | Add missing validation pattern to links.target member (see [Issue 271](https://github.com/eiffel-community/eiffel/issues/271)). |
| 4.1.0 | [edition-lyon](../../../tree/edition-lyon) | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as for ActF

| 3.2.0 | Current version | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 3.1.0 | Current version | Add `data.persistentLogs.{mediaType,tags}`. |
| 3.2.0 | [edition-lyon](../../../tree/edition-lyon) | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 3.1.0 | [edition-lyon](../../../tree/edition-lyon) | Add `data.persistentLogs.{mediaType,tags}`. |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as for ActF

| 3.2.0 | Current version | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 3.1.0 | Current version | Add `data.liveLogs.{mediaType,tags}`. |
| 3.2.0 | [edition-lyon](../../../tree/edition-lyon) | Add links.domainId member (see [Issue 233](https://github.com/eiffel-community/eiffel/issues/233)). |
| 3.1.0 | [edition-lyon](../../../tree/edition-lyon) | Add `data.liveLogs.{mediaType,tags}`. |

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as for ActF

@e-backmark-ericsson
Copy link
Member

Milestones are just containers of issues and PRs so it depends on how we want to use the milestones. So far the Lyon milestone has only contained issues and no PRs so to stick with that ad hoc convention we should leave this PR out (but add the #272 issue).

Ok. Fair enough. We should document our WoW around milestones - #279

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Release Lyon edition of protocol
4 participants