Skip to content

Reorder & normalize Changelog - #180

Open
PragTob wants to merge 1 commit into
michalmuskala:masterfrom
PragTob:patch-1
Open

Reorder & normalize Changelog#180
PragTob wants to merge 1 commit into
michalmuskala:masterfrom
PragTob:patch-1

Conversation

@PragTob

@PragTob PragTob commented Dec 23, 2023

Copy link
Copy Markdown
Contributor
  • ordered changelog by version number, not sure if there is a general rule but having 1.4.1 inbetween the two 1.5 alpha releases felt weird
  • standardized the format, so that it has "Enhancements" like the previous releases

* ordered changelog by version number, not sure if there is a general rule but having 1.4.1 inbetween the two 1.5 alpha releases felt weird
* standardized the format, so that it has "Enhancements" like the previous releases
@PragTob

PragTob commented Aug 7, 2024

Copy link
Copy Markdown
Contributor Author

@michalmuskala 👋 Also just noticed that the newest 1.4 release changelog entries aren't on main which is a bit confusing coming in. Any interest in porting these over or the initial change here? :)

Take care! 💚

@michalmuskala

Copy link
Copy Markdown
Owner

Yeah, it's a bit of a mess currently since main is the code for the, 1.5 branch which I don't think will move forward, and the 1.4 branch has the separate patches, and where the changelog for that branch lives.
TBH I'm not really sure what's the best way forward here

@PragTob

PragTob commented Aug 13, 2024

Copy link
Copy Markdown
Contributor Author

I personally think that backporting the changelog from branches to main for released versions is good practice, as that's what most people will go to/see and it'd be nice to have one "complete" changelog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants