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

Add a static CHANGELOG.md containing the release history #723

Closed
SebastianBezold opened this issue Aug 22, 2023 · 3 comments
Closed

Add a static CHANGELOG.md containing the release history #723

SebastianBezold opened this issue Aug 22, 2023 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@SebastianBezold
Copy link
Contributor

Is your feature request related to a problem? Please describe.
TRG 1.03 describes, that every Tractus-X repo must contain a CHANGELOG.md file, that contains a short overview of the current and past releases.
The info present on the GitHub releases like for example on 0.5.0 is really good. It can be used "as-is" in the CHANGELOG.md as well.

Describe the solution you'd like
As far as I can remember, there has been a CHANGELOG.md for the Tractus-X EDC in the past. If this can still be found, I think it should be added again and the current 0.5.0 release info added as well.

Describe alternatives you've considered
Replacing the CHANGELOG.md by just having the change description on the GitHub release would remove the possibility to browse easily through the release history. One would have to go through all of the GitHub releases (also RCs), which is just not as convenient as having it in one place

Additional context
Add any other context or screenshots about the feature request here.

blocks #714

@SebastianBezold
Copy link
Contributor Author

Hi @dsukhoroslov, thanks for pointing that out. So it seems, the CHANGELOG.md will be added again. This is a good thing, because the decision is actually violating the project rules (which is the release Guidelines). So I hope this is not too much effort. The auto-generated release notes on a GitHub release seem quite well structured, so I think they can just be copy/pasted to the CHANGELOG, so the release history is continued

@wolf4ood
Copy link
Contributor

closed by #733

@github-project-automation github-project-automation bot moved this from In Progress to Done in EDC Board Aug 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

No branches or pull requests

4 participants