Cwa-app-android: Mention changes in release commits (Best practice)

[corneliusroemer]

You're not abiding by best practices when you're not mentioning changes in your release commits.

Please mention:

• Which bugs were fixed
• Which new features are enabled
• other noteworthy points

Otherwise public testers won't be able to verify fixes and test new features before they go live, swamping you with error reports.

[tkowark]

Hi @corneliusroemer , thanks for the suggestion. We'll discuss with the dev team. In the meantime, could you kindly select the enhancement template for suggestions? Just makes searching for us a bit easier. Thanks a lot in advance!

[corneliusroemer]

Thanks!
And it'd be great if you also considered adding apk's for releases, so that we, the tech public, can help you spot problems early on, before rollout.

[tkowark]

You mean like the ones mentioned in #514 ? (just making the link explicit ;) )

[corneliusroemer]

For example, or the location permission issue that has led to misunderstandings. Or we could have a list of incompatible devices ready so that people don't waste time trying and get frustrated. And have troubleshooting information ready for various error messages.

[corneliusroemer]

If I see it correctly, version bump 1.0.3 was again not accompanied by any meaningful commit message. I thought providing meaningful commit messages/changelogs was Git101 - why don't you implement it? https://github.com/corona-warn-app/cwa-app-android/pull/663

@tkowark you mentioned above (3d ago) that you're going to discuss with the dev team. Could you update us about progress of that discussion?

Actually, this issue should probably also be moved over to documentation since it impacts best practice for all parts of this project.

[jakobmoellersap]

Release Notes provided in https://github.com/corona-warn-app/cwa-app-android/releases/tag/1.0.3

[tkowark]

Since release notes are now provided in the release description, we're going to close this issue. Of course, if future releases deviate from that best practice again, we are thankful for a friendly reminder. Thank you very much for spotting such seemingly small issues that make a large difference with regards to transparency.