Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a change log #1909

Closed
idg10 opened this issue Apr 3, 2023 · 0 comments · Fixed by #1933
Closed

Add a change log #1909

idg10 opened this issue Apr 3, 2023 · 0 comments · Fixed by #1933
Assignees
Milestone

Comments

@idg10
Copy link
Collaborator

idg10 commented Apr 3, 2023

Although GitHub automatically generates a list of changes for us when we create a release, there's a problem with this: it doesn't capture any context around why particular changes went into a particular release.

For anyone picking up maintenance of this project (e.g., me at the start of this year) the absence of this kind of background can make some decisions hard to comprehend.

So starting with V6, we want to try to capture a release history that describes the goals of any particular release, to complement the automatically generate list of specific technical changes.

@idg10 idg10 added the [area] Rx label Apr 3, 2023
@idg10 idg10 added this to the Rx 6.0 milestone Apr 3, 2023
@idg10 idg10 self-assigned this Apr 3, 2023
idg10 added a commit that referenced this issue May 16, 2023
The release notes resolve #1909

The readme update partially addresses #1881
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant