You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find it difficult to understand and track the changes made in Molecule with the current changelog posted on the Github release page.
The changes described in the release page are not enough from both a user and developer perspective.
Migrations instructions or breaking changes are not properly documented, for example this commit 21dcd2b is "Removing support for custom templating from drivers", but this is not detailed in the GitHub release page.
That said, as a developer, I have no problem browsing the commit history, even though it's not as friendly as a changelog.
I would like to propose that this project starts to maintain a changelog file and use tools to help.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I find it difficult to understand and track the changes made in Molecule with the current changelog posted on the Github release page.
The changes described in the release page are not enough from both a user and developer perspective.
Migrations instructions or breaking changes are not properly documented, for example this commit 21dcd2b is "Removing support for custom templating from drivers", but this is not detailed in the GitHub release page.
That said, as a developer, I have no problem browsing the commit history, even though it's not as friendly as a changelog.
I would like to propose that this project starts to maintain a changelog file and use tools to help.
Beta Was this translation helpful? Give feedback.
All reactions