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

fix: tidy up release steps #2470

Open
2 tasks
SgtPooki opened this issue Apr 27, 2023 · 2 comments
Open
2 tasks

fix: tidy up release steps #2470

SgtPooki opened this issue Apr 27, 2023 · 2 comments
Labels
effort/days Estimated to take multiple days, but less than a week kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up

Comments

@SgtPooki
Copy link
Member

SgtPooki commented Apr 27, 2023

We should tidy up our release steps so that automating ipfs-desktop release will be more simple.

Automating changelog creation saves time and ensures accuracy. It's also important to include "docs" commits in each release, so changes are well-documented and easy to find. These simple steps can make the release process smoother and more efficient.

Some existing efforts pushed to https://github.com/ipfs/ipfs-desktop/tree/feat/changelog-automation

Tasks

@SgtPooki SgtPooki added the need/triage Needs initial labeling and prioritization label Apr 27, 2023
@whizzzkid
Copy link
Contributor

@SgtPooki a release-pr (like on ipfs-companion) can be helpful I believe.

@whizzzkid whizzzkid added P1 High: Likely tackled by core team if no one steps up kind/enhancement A net-new feature or improvement to an existing feature effort/days Estimated to take multiple days, but less than a week and removed need/triage Needs initial labeling and prioritization labels May 3, 2023
@SgtPooki
Copy link
Member Author

SgtPooki commented May 9, 2023

This was a small piece i wanted to write out that is going to be needed regardless of release please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/days Estimated to take multiple days, but less than a week kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up
Projects
No open projects
Status: Needs Grooming
Development

No branches or pull requests

2 participants