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.

Sign up for GitHub

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

Jump to bottom

[899] Add support for ConcernUsage in diagram 'General View' #928

Merged
merged 1 commit into from
Jan 7, 2025
Merged

[899] Add support for ConcernUsage in diagram 'General View' #928

merged 1 commit into from
Jan 7, 2025

Conversation

flatombe
Copy link
Contributor

This is meant to be merged after #927.

PLEASE READ ALL ITEMS AND CHECK ONLY RELEVANT CHECKBOXES BELOW

Project management

  • Has the pull request been added to the relevant milestone?
  • Have the priority: and pr: labels been added to the pull request? (In case of doubt, start with the labels priority: low and pr: to review later)
  • Have the relevant issues been added to the pull request?
  • Have the relevant labels been added to the issues? (area:, type:)
  • Have the relevant issues been added to the same project milestone as the pull request?

Changelog and release notes

  • Has the CHANGELOG.adoc + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc been updated to reference the relevant issues?
  • Have the relevant API breaks been described in the CHANGELOG.adoc + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?
  • In case of a change with a visual impact, are there any screenshots in the doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?
  • In case of a key change, has the change been added to Key highlights section in doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?
  • Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?

Documentation

  • Have you included an update of the documentation in your pull request? Please ask yourself if an update (installation manual, user manual, developer manual...) is needed and add one accordingly.

Tests

  • Is the code properly tested? Any pull request (fix, enhancement or new feature) should come with a test (or several). It could be unit tests, integration tests or cypress tests depending on the context. Only doc and releng pull request do not need for tests.

@AxelRICHARD AxelRICHARD added this to the 2025.2.0 milestone Dec 23, 2024
@flatombe flatombe force-pushed the dev/PR3 branch 6 times, most recently from 7639792 to 7198c78 Compare January 6, 2025 16:39
@flatombe @AxelRICHARD
[899] Add ConcernUsage to General View
95b15ca 
* 'ConcernUsage' is essentially a 'RequirementUsage', both
semantically and graphically.
* Update the changelog and release notes accordingly.

Associated tests should validate the creation, in the 'General View'
diagram, of ConcernUsage nodes and of sub-nodes in its compartments.

Bug: eclipse-syson#899
Signed-off-by: Florent Latombe <[email protected]>
@AxelRICHARD AxelRICHARD merged commit 520042f into eclipse-syson:main Jan 7, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
pr: to review later priority: low
Projects
None yet
Milestone
2025.2.0
Development

Successfully merging this pull request may close these issues.
2 participants
@flatombe @AxelRICHARD