-
Hello couchbase team,
Would be nice to keep track of changes happening in this repo in a changelog file, or if you start creating releases in GitHub, you can include the list of changes in each r…
-
#### Brief summary of issue / Description of requested feature:
1. Testers ask for recent changes to a release candidate.
2. We can only show commits. These have noise.
#### Reasons for adding f…
Kebap updated
2 years ago
-
We should keep track of all changes by keeping a changelog. I thought about using the spec listed on http://keepachangelog.com/ . The spec contains a section of unreleased changes which can be maintai…
-
think things are stable enough to start keeping a high-level changelog?
whenever we are, this is a not-entirely-terrible standard: http://keepachangelog.com/
-
As the number of users of the package is growing, I think we need to consider how to notify the changes in each release in a more organized form. It is time to discuss alternatives for keeping a chang…
-
It would help people evaluating upgrading if a changelog was kept. For example, one of the last releases had a major version upgrade. This implies possibly breaking changes, but documentation is found…
-
Would be nice to have detailed changelogs in the [DSPy Releases page](https://github.com/stanfordnlp/dspy/releases), generated with one shell command with [commitizen](https://commitizen-tools.github.…
-
I rely on this for a production app and would like to know what changes are coming into the project.
I suggest the format at http://keepachangelog.org
-
4.0 was released which implies breaking changes, but there is no CHANGELOG, NEWS or HISTORY file, and the Github Releases page doesn't contain change history either.
Changelogs in some form are a t…
-
I can't find information on what has changed in any given published release. It would be nice if HK2 kept a change log that conforms to http://keepachangelog.com/en/0.3.0/ specification