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

Changelog - Hand Curate vs Autogenerate vs Require on PRs #3147

Open
ianhi opened this issue Mar 4, 2021 · 2 comments
Open

Changelog - Hand Curate vs Autogenerate vs Require on PRs #3147

ianhi opened this issue Mar 4, 2021 · 2 comments

Comments

@ianhi
Copy link
Contributor

ianhi commented Mar 4, 2021

At the widgets meeting on March 4 there was discussion of autogenerating a changelog or perhaps enforcing manual curation on PRs.

jupyter-widgets/team-compass#1 (comment)

Opening this issue to discuss what if we should:

  1. Keep the current manual curation at release time
  2. Move to some sort of autogenerating changelog
  3. Require PRs to include adding a brief description to changelog (what matplotlib does)
@jasongrout
Copy link
Member

For reference, here is what I've been doing, at least for getting a changelog curation for recent RCs, building on our experience doing the changelog for jlab: https://ipywidgets.readthedocs.io/en/latest/dev_release.html#changelog

@jasongrout
Copy link
Member

One issue is that often the PRs are not assigned to the correct milestone, etc., so often there is a manual curation step just for that. We could also automate some of that (check where a commit was merged into a tree, and make sure the PR is assigned to the corresponding milestone).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants