Tracking changes between TWBlue releases

[Arfs6]

We have a working github release workflow now. The first issue I've seen wihth it is some changes weren't mentioned.
My question is, what is the best way to keep track of the changes between releases? Discussions? Milestones? Issues?
One of the critical change that is not in the release note is TWBlue installers wouldn't work in 32 bit processors. And there are some other missing info here and there.

[manuelcortez]

Hi, personally I like the Issue Workflow (create an issue for new changes (wen those changes are more than a few lines), discuss if others have an opinion abou this, and open a pr based in that issue). I normally update the changelog manually (still have this new one pending btw).

[Arfs6]

I also like the issues based workflow. I guess a solution to what I am saying is to get a list of all closed issues from the previous release, and use it to generate a change log. To clarify, the problem I am trying to point out is with tracking the changes, knowing all that changed between releases. For example, show user profile dialog, update profile dialog and searching were all implemented, and I don't think it was included in the change log. Something I am thinking of is having a new issue or discussion after a release and name it, for example, changes after 2023.12.30. Then for each succesful bug fix or new featture, the author should add it to the issue / discussion. When it's time for a new release, you'll just have to open this issue / discussion and all the changes are in one place. What do you think? P.S. I am replying to this from phone, I hope I won't regret this :)

…

On Sun, 31 Dec 2023, 3:21 pm Manuel Cortéz, ***@***.***> wrote: Hi, personally I like the Issue Workflow (create an issue for new changes (wen those changes are more than a few lines), discuss if others have an opinion abou this, and open a pr based in that issue). I normally update the changelog manually (still have this new one pending btw). — Reply to this email directly, view it on GitHub <#568 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2NJ653GK6DO6TBRDVHR3ZLYMFYIFAVCNFSM6AAAAABBIE2ETKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSHE3DANZRGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Arfs6]

Lol I thought V2023.4.13 was built with the latest commit on next-gen. Regardless, I still think doing something like this will be usefull. The latest release, version 2024.01.05 is still missing some fixes in the change log.