docs: Add CHANGELOG.md file#3335
docs: Add CHANGELOG.md file#3335lucydodo merged 1 commit intosqlitebrowser:masterfrom richb-hanover:add-changelog
Conversation
|
LGTM. I apologize for the late review. |
|
Cool, 😄 |
justinclift
added
the
item for release note
|
@lucydodo @justinclift I just looked at the updated CHANGELOG. WOW! That's a lot of work that has been completed! I think there's a lot of good stuff there that isn't available to people (like me) who are only willing to use the Release Version. Have you considered making a new release? What would be involved? Thanks. |
|
A new release 'is in the works'. We're just clearing the decks of other issues so focus can be put getting the release done. |
|
Yes, we are working on a new release. 😄 |
|
This is great news. No need to rush for me. Thanks! |
4 participants
As suggested in #3334, a CHANGELOG.md file makes it easy for newcomers and occasional users to see the status of the nightly builds versus the stable, released version.
My advice is that the CHANGELOG contain user-facing changes (updates to SQLite, new features, bug fixes, etc) but not changes to the documentation, build process, etc. since they're not as interesting to casual users. Other developers can always check the PR logs to see exactly what has changed.
The beauty of keeping this file up to date is that when the time comes to release a new version, it's fairly straightforward to review and update the Unreleased - nightly section to produce the first cut of the announcement for the new version.