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

Speed up release cycles ♻️ #532

Closed
3 tasks done
JamieSlome opened this issue Apr 23, 2024 · 5 comments · Fixed by #534
Closed
3 tasks done

Speed up release cycles ♻️ #532

JamieSlome opened this issue Apr 23, 2024 · 5 comments · Fixed by #534
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@JamieSlome
Copy link
Member

JamieSlome commented Apr 23, 2024

Observations 👀

Our current release cycle is slow and is unduly held up by the implementation of large changes sets. In order to release new features and bug improvements today, we use the published GitHub event via GitHub releases to trigger an NPM publication.

This can be found in our GitHub workflows here 👈

Requirements 📝

In order to speed up our release cycles and follow open source best practices we should:

Tasks

@JamieSlome JamieSlome added help wanted Extra attention is needed good first issue Good for newcomers labels Apr 23, 2024
@JamieSlome
Copy link
Member Author

@eddie-knight @maoo - just pinging you for your awareness! 👍

@maoo
Copy link
Member

maoo commented Apr 25, 2024

Thanks @JamieSlome - checkout #534 , it probably checks all your boxes.

In parallel, can we set some target dates for future releases?

1.3.0 - reconciled code - May 3rd
1.4.0 - CLI and API - May 31st
2.0.0-alpha - plugins and much more - September 27th

@coopernetes @msagi @JamieSlome - did I miss any important milestone? you think that dates are realistic?

@JamieSlome
Copy link
Member Author

@eddie-knight - looks like the GitHub automatic versioning works nicely 👍

Not sure why the NPM publish failed?

On a side note, should we add an ignore list for files like .github as we likely don't want to release for these?

@JamieSlome
Copy link
Member Author

@eddie-knight - fabulous job on this and appreciate the follow up minor improvements ❤️

@TheJuanAndOnly99 @maoo - are we able to make PR / Validate & Label PR (pull_request_target) a required status check for pull requests?

@maoo
Copy link
Member

maoo commented May 10, 2024

@eddie-knight - fabulous job on this and appreciate the follow up minor improvements ❤️

@TheJuanAndOnly99 @maoo - are we able to make PR / Validate & Label PR (pull_request_target) a required status check for pull requests?

Done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants