Add CHANGELOG.md #54
Add CHANGELOG.md #54
Conversation
|
Any updates on this? What is your plan regarding the merge? Ref: #38 (comment) |
|
Andreas, good morning. How are you? We now have two branches: a stable master and a development. Now it's the right time to follow your idea. If you can, please describe the final result and effect to the project. Soon you do it, we review the description and example of final result. The second step is to review the development code (dev branch) and submit a PR to there. After reviewing, we can bring changes into the master branch. I hope you're good, healthy and safe. Have a great day. Best regards, Alexandre. |
|
Are you kidding me? This is ridiculous. Look, take the change or let it be, let it be. A small change like adding a change log involved me now for nearly 2 years? I opened an issue to discuss the change in January 2023, then a first a PR against master in March 2023. It was not what you want. Later you wrote in July 2024
I did exactly that on the same day after you wrote it. PR against dev. And now you require yet another description and PR against dev?! Let it be |
Add new changelog to the repository. It helps seeing the changes per release and it's easier to see the status of the project.
You can then link to the CHANGELOG.md file in the header section of the readme and also link the sections in the release notes.
You can even update the changelog in the unreleased section to keep the users up to date with the latest, but not yet published changes. After you build a new version, you can rename the unreleased section to the current release with the date and use the template part in the changelog for a new unreleased section. Easy.
Closes #38