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

0.3.0 Release Plan #991

Closed
jtpio opened this issue Oct 5, 2021 · 19 comments
Closed

0.3.0 Release Plan #991

jtpio opened this issue Oct 5, 2021 · 19 comments
Milestone

Comments

@jtpio
Copy link
Member

jtpio commented Oct 5, 2021

0.3.0a0 was just published: https://github.com/voila-dashboards/voila/releases/tag/v0.3.0a0

main now targets the 0.3.0 release. And there is the 0.2.x branch to cut new patch releases for 0.2 if needed (0.2.17, 0.2.18, ...).

0.3.0 milestone

For issues and PRs that should go to the 0.3.0 release, we add them to the 0.3.0 milestone: https://github.com/voila-dashboards/voila/milestone/4

This 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-release

We 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 release 0.3.0a1, we do the following:

Draft Changelog

With next as the version spec:

image

We then wait for:

  1. the PR to be created on the repo. Example: Automated Changelog Entry for 0.3.0a0 on main #990
  2. Tests to pass
  3. Merge the changelog PR

Full Release

Using the information in the body of the changelog PR, for example:

image

We use the Full Release workflow:

image

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.x

Making a new 0.2.x release

We 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.

@jtpio jtpio added this to the 0.3.0 milestone Oct 5, 2021
@jtpio jtpio pinned this issue Oct 5, 2021
@jtpio jtpio changed the title Release 0.3.0 0.3.0 Release Plan Oct 14, 2021
@trungleduc
Copy link
Member

Hi all, with the recent changes ( #936 #999 ) about the new preheated kernel mode, the backend of Voila is refactored intensively. Should we shorten the release cycle of Voila and push the frontend refactoring (#846 ) to 0.4.0 ?

@jtpio
Copy link
Member Author

jtpio commented Oct 14, 2021

Should we shorten the release cycle of Voila and push the frontend refactoring (#846 ) to 0.4.0 ?

Pushing #846 to 0.4.0 sounds good to me, there are still a couple of things to fix there.

I think we should still go through the alpha -> beta -> rc release cycle. If we want to shorten then we can start releasing 0.3.0bx, and then 1-2 weeks later rc and final. But once in beta we should not add new breaking changes.

@SylvainCorlay
Copy link
Member

+1 on both proposals

@trungleduc
Copy link
Member

Pushing #846 to 0.4.0 sounds good to me, there are still a couple of things to fix there.

I think we should still go through the alpha -> beta -> rc release cycle. If we want to shorten then we can start releasing 0.3.0bx, and then 1-2 weeks later rc and final. But once in beta we should not add new breaking changes.

Yes I mean shorten the feature list but not the release process.

@jtpio
Copy link
Member Author

jtpio commented Oct 14, 2021

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 0.3.0.

@jtpio
Copy link
Member Author

jtpio commented Oct 14, 2021

Thanks @trungleduc for taking care of the 0.3.0a2 release!

@trungleduc
Copy link
Member

0.3.0 milestone is clean, we can release 0.3.0b0 now?

@jtpio
Copy link
Member Author

jtpio commented Oct 27, 2021

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 release as the spec in the releaser workflows (first the changelog then the full release).

@trungleduc
Copy link
Member

ok, I'll do it.

@trungleduc
Copy link
Member

0.3.0b0 is out!

@jtpio
Copy link
Member Author

jtpio commented Oct 28, 2021

Nice, thanks @trungleduc!

@trungleduc
Copy link
Member

Hello all, 0.3.0rc0 is released today. The release candidate phase is planned for about 2 weeks and we will try to have the final by early December.

@trungleduc
Copy link
Member

trungleduc commented Dec 8, 2021

Hello all, we had 3 weeks of RC for now, is it ok for you to release the final version?

@jtpio
Copy link
Member Author

jtpio commented Dec 8, 2021

Sounds good!

Let's get these 2 PRs in first?

@trungleduc
Copy link
Member

trungleduc commented Dec 8, 2021

Yes, I want to do a quick pass for the tests on Windows too.

@jtpio
Copy link
Member Author

jtpio commented Dec 9, 2021

The version spec to use in the releaser to make the final release will be release.

@trungleduc
Copy link
Member

Thanks @jtpio, will do it today.

@jtpio
Copy link
Member Author

jtpio commented Dec 13, 2021

Closing as 0.3.0 has now been released: https://github.com/voila-dashboards/voila/releases/tag/v0.3.0

Thanks @trungleduc!

@jtpio jtpio closed this as completed Dec 13, 2021
@jtpio jtpio unpinned this issue Dec 13, 2021
@jtpio
Copy link
Member Author

jtpio commented Dec 13, 2021

Create a new 0.3.x milestone to track future 0.3.x patches: https://github.com/voila-dashboards/voila/milestone/6

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

3 participants