Restore CHANGELOG
See original GitHub issueIn a recent tidy-up of this repo we lost the CHANGELOG
in the root.
I think this is a shame, for two reasons:
- We lost a visible historical record (“it’s in the git history” doesn’t count as visible) of the evolution of our core IP over the past 8 years
- We have lost a prominent place to log the ongoing changes we are making to this repo (for example @adatzer’s great work on discoverability via git submodule updates)
I propose:
- Resurrecting the historic CHANGELOG
- Backfilling entries since its deletion
- Adding new entries as we make updates to this repo
For new entries in the CHANGELOG, I would propose simply datestamping them given that they don’t fall under specific release numbers any more (there is no global Snowplow release version at the level of this repo currently - we don’t offer LTS / blessed bundles to OSS yet).
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
iOS update and restore errors - Apple Support
iOS update and restore errors · Try these steps first · Choose your error number or message · Update the software on your...
Read more >StoreChangelogReader · The Internals of Kafka Streams
With at least one changelog partition that needs restoring, restore requests the restore Consumer to fetch data for the changelog partitions ( KafkaConsumer....
Read more >Restore a previous version of a file without unwanted changes
Restore a previous version of a file without unwanted changes · Open the file you want to restore and go to File >...
Read more >Restore CD changelog - UrBackup
Fix restore of whole disk images; Use local time from server for displaying image time instead of local restore OS time. 2.4.0. Changes:...
Read more >git restore - Discard or unstage uncommitted local changes
The "restore" command helps to unstage or even discard uncommitted local changes. On the one hand, the command can be used to undo...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Maybe we put a placeholder at the top of the CHANGELOG explaining what we are planning and linking off elsewhere (
/releases
?) until such time as we have the more narrative-driven version…We should do this (and automate it) when we automate the updating of the submodules, which we’ve just started working on (cc @adatzer).
I’d suggest introducing a CHANGELOG.json too as this will make autogenerating the CHANGELOG.md far easier and more reliable.