-
Notifications
You must be signed in to change notification settings - Fork 497
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
0.3.0 Release Plan #991
Comments
Pushing #846 to I think we should still go through the alpha -> beta -> rc release cycle. If we want to shorten then we can start releasing |
+1 on both proposals |
Yes I mean shorten the feature list but not the release process. |
Alright sounds good, thanks for the clarifications 👍 We could also do a quick pass on the open PRs and see if some of them could make it to |
Thanks @trungleduc for taking care of the |
0.3.0 milestone is clean, we can release |
Thanks @trungleduc for clearing the remaining items and reporting here. Looks like we should indeed be able to bump. In that case we can use |
ok, I'll do it. |
|
Nice, thanks @trungleduc! |
Hello all, |
Hello all, we had 3 weeks of RC for now, is it ok for you to release the final version? |
Sounds good! Let's get these 2 PRs in first? |
Yes, I want to do a quick pass for the tests on |
The version spec to use in the releaser to make the final release will be |
Thanks @jtpio, will do it today. |
Closing as Thanks @trungleduc! |
Create a new |
0.3.0a0
was just published: https://github.com/voila-dashboards/voila/releases/tag/v0.3.0a0main
now targets the0.3.0
release. And there is the0.2.x
branch to cut new patch releases for0.2
if needed (0.2.17
,0.2.18
, ...).0.3.0
milestoneFor issues and PRs that should go to the
0.3.0
release, we add them to the0.3.0
milestone: https://github.com/voila-dashboards/voila/milestone/4This will be the case for anything major, or a PR that introduces backward incompatible changes with
0.2.x
.Making a new
0.3.0
pre-releaseWe use the Jupyter Releaser as documented in:
https://github.com/voila-dashboards/voila/blob/main/RELEASE.md#using-jupyter_releaser
As an example, the current version is
0.3.0a0
. If we want to release0.3.0a1
, we do the following:Draft Changelog
With
next
as the version spec:We then wait for:
Full Release
Using the information in the body of the changelog PR, for example:
We use the Full Release workflow:
Backporting changes to
0.2.x
We use https://github.com/meeseeksbox to backport changes to the
0.2.x
branch if needed: https://github.com/voila-dashboards/voila/tree/0.2.xMaking a new
0.2.x
releaseWe use the Jupyter Release, specifying the
0.2.x
when launching the workflows.cc @voila-dashboards/voila-core
Let me know if all of this makes sense, and if you would like to cut new releases with the releaser and need guidance. Don't hesitate to comment here otherwise.
The text was updated successfully, but these errors were encountered: