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

Setup automatic release notes handling #1165

Closed
Tracked by #1158
ztefanie opened this issue Oct 12, 2023 · 9 comments · Fixed by #1390
Closed
Tracked by #1158

Setup automatic release notes handling #1165

ztefanie opened this issue Oct 12, 2023 · 9 comments · Fixed by #1390
Assignees
Labels
CI/CD discussion-needed We need to resolve the questions in the issue. Task

Comments

@ztefanie
Copy link
Member

Think of a good way to handle release notes.

Options:

  1. Automatic handling like in integreat can be done. We can add a field to which apps a release note belongs
  2. We can not handle release notes automatically. So it needs to be done manually.

Other options?

@ztefanie ztefanie added Task discussion-needed We need to resolve the questions in the issue. CI/CD labels Oct 12, 2023
@ztefanie ztefanie mentioned this issue Oct 12, 2023
30 tasks
@sarahsporck
Copy link
Contributor

Alternative -> https://docs.github.com/de/rest/releases/releases?apiVersion=2022-11-28#generate-release-notes-content-for-a-release
But this cannot generate different release notes per app of course.

@ztefanie
Copy link
Member Author

ztefanie commented Nov 9, 2023

@sarahsporck Are different release notes needed for entitlementcard and nuernberg?

@sarahsporck
Copy link
Contributor

currently we use the same release notes for both applications. I guess there are use cases for different release notes, but currently not really a thing. What do you think @f1sh1918

@f1sh1918
Copy link
Contributor

f1sh1918 commented Nov 10, 2023

Yes we definitly need release notes per project. I set the stores notes manually in the stores and they differ quite often. I think we also need native & administration. So in the end we should have in mattermost 4 notifications. 2 for each project

@sarahsporck
Copy link
Contributor

Yes we definitly need release notes per project. I set the stores notes manually in the stores and they differ quite often. I think we also need native & administration. So in the end we should have in mattermost 4 notifications. 2 for each project

Then I think the github enpoint is not an option and we should use the same approach as in Integreat.

@f1sh1918
Copy link
Contributor

additionally to sarahs post, i don't think that the release notes that are generated contain suitable wording for store release notes that are understandable for users.
I know that we discussed a lot about this topic but i think we should use the same approach that in integreat @ztefanie ?!

@ztefanie
Copy link
Member Author

ztefanie commented Mar 26, 2024

We can think about / discuss this, not sure if it is worth the effort.

@f1sh1918
Copy link
Contributor

We can think about / discuss this, not sure if it is worth the effort.

Hm i think we also could use a general description for the releases in the stores. Like
"Wir arbeiten kontinuierlich daran die App zu verbessern...etc"

@f1sh1918 f1sh1918 moved this from Next Up to In Progress in entitlementcard Apr 10, 2024
@ztefanie
Copy link
Member Author

We can think about / discuss this, not sure if it is worth the effort.

Hm i think we also could use a general description for the releases in the stores. Like "Wir arbeiten kontinuierlich daran die App zu verbessern...etc"

I think we can start with this, as it is good enough, we also can add a link to the releases page
with a hint, "for a details list of improvments, feel free to checkout out https://github.com/digitalfabrik/entitlementcard/releases"
or something similar, if we later in the future, need / want the improvements in the stores, we can still do it. So I think the easier way is good enough for now.

@f1sh1918 f1sh1918 moved this from In Progress to In Review in entitlementcard Apr 15, 2024
@github-project-automation github-project-automation bot moved this from In Review to Done in entitlementcard Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI/CD discussion-needed We need to resolve the questions in the issue. Task
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants