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.

Sign up for GitHub

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

Jump to bottom

Ensure releases use up-to-date CHANGELOG.md #269

Open
guseggert opened this issue Apr 5, 2023 · 1 comment
Open

Ensure releases use up-to-date CHANGELOG.md #269

guseggert opened this issue Apr 5, 2023 · 1 comment
Assignees
@galargh
Labels
dif/medium Prior experience is likely helpful P1 High: Likely tackled by core team if no one steps up topic/build-and-release-fitness Items related to our CI process, dependency management, etc.

Comments

@guseggert
Copy link
Contributor

See: https://github.com/pl-strflt/changelog-driven-release

We should onboard with this so that we just flip a version in the changelog and the release happens. I think there are two done criteria for this:
@guseggert guseggert added need/triage Needs initial labeling and prioritization P1 High: Likely tackled by core team if no one steps up dif/medium Prior experience is likely helpful and removed need/triage Needs initial labeling and prioritization labels Apr 5, 2023
@guseggert guseggert self-assigned this Apr 5, 2023
@guseggert guseggert mentioned this issue Apr 5, 2023
Closed
@BigLep BigLep added the topic/build-and-release-fitness Items related to our CI process, dependency management, etc. label Apr 6, 2023
@galargh galargh assigned galargh and unassigned guseggert May 15, 2023
@galargh galargh changed the title Use CHANGELOG.md to drive releases Ensure releases use up-to-date CHANGELOG.md May 15, 2023
@galargh
Copy link
Contributor

galargh commented May 15, 2023

As explained in the child issues, we're going to stick to using release process from UCI but we're going to expand it so that it can work well together with CHANGELOG.md that we're going to keep up-to-date through automation.

@BigLep BigLep mentioned this issue Aug 3, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@galargh galargh

Labels
dif/medium Prior experience is likely helpful P1 High: Likely tackled by core team if no one steps up topic/build-and-release-fitness Items related to our CI process, dependency management, etc.
Projects
No open projects
IPFS Shipyard Team
Status: 🔎 In Review
Milestone
No milestone
Development

No branches or pull requests
3 participants
@BigLep @guseggert @galargh