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.5.0 Release Plan #1245

Closed
martinRenou opened this issue Oct 28, 2022 · 21 comments
Closed

0.5.0 Release Plan #1245

martinRenou opened this issue Oct 28, 2022 · 21 comments
Labels
enhancement New feature or request Release plan
Milestone

Comments

@martinRenou
Copy link
Member

Problem

0.4.0 was out a couple of days ago and we already started merging breaking changes!

We should start considering making an 0.5.0 release.

Proposed Solution

This is the milestone for 0.5.0 https://github.com/voila-dashboards/voila/milestone/10

We can start adding issues and PRs to it.

@martinRenou martinRenou added the enhancement New feature or request label Oct 28, 2022
@martinRenou
Copy link
Member Author

Thoughts about including the Voila + FPS PR into this milestone? #984

@martinRenou
Copy link
Member Author

We could also include the Voilite work into this release #1187

@jtpio jtpio added this to the 0.5.0 milestone Oct 28, 2022
@martinRenou
Copy link
Member Author

The first alpha is out https://github.com/voila-dashboards/voila/releases/tag/v0.5.0a0

@martinRenou
Copy link
Member Author

I'm working on including #1249

@mangecoeur
Copy link

Hi, I'd be interested in the FPS functionality being merged into Voila, I would be happy to help in any way I can! I'm especially interested in combing voila with FPS Auth.

@jtpio jtpio pinned this issue Mar 16, 2023
@trungleduc
Copy link
Member

@mangecoeur we had a PR to integrate FPS into voila (#984). But since we are dropping FPS in favor of another framework (jupyter-server/jupyverse#277), FPS won't be maintained anymore (jupyter-server/fps#50). We will come back to this subject once jupyverse is stabilized.

@trungleduc
Copy link
Member

@jtpio @martinRenou I opened an issue (#1304) for migrating voila to lab 4.

@jtpio
Copy link
Member

jtpio commented Mar 16, 2023

Sounds good thanks @trungleduc.

@jtpio
Copy link
Member

jtpio commented Mar 24, 2023

Adding #539 to the milestone to have it on the radar.

We should check Voila can run offline or in self-contained mode that doesn't make requests to external services. Hopefully should be easier now with #846.

This was also brought in https://discourse.jupyter.org/t/running-voila-without-internet/13823.

@martinRenou
Copy link
Member Author

0.5.0a5 is out with the JupyterLab 4 migration! https://pypi.org/project/voila/0.5.0a5

Congrats @trungleduc !

@martinRenou
Copy link
Member Author

@mariobuikhuizen @maartenbreddels friendly ping :)

We just released 0.5.0a5, I wonder if you would have the same issue with this one you had before.

If you have time to test it that'd be great!

@mariobuikhuizen
Copy link
Member

Thanks for the ping @martinRenou. For voila-vuetify and ipypopout we hook in to the internals of the voila frontend code, which has substantially changed. We have to make changes to voila-vuetify and ipypopout to make it compatible with the new frontend code. I don't think this can be fixed in voila and also isn't a defect in voila, so it shouldn't block the release of 0.5.0.

@martinRenou
Copy link
Member Author

We may want to try including fixes for the following issues (that may be easy to fix with the new usage of JupyterLab mime renderers):

@martinRenou
Copy link
Member Author

Adding #539 to the milestone to have it on the radar.
We should check Voila can run offline or in self-contained mode that doesn't make requests to external services. Hopefully should be easier now with #846.
This was also brought in https://discourse.jupyter.org/t/running-voila-without-internet/13823.

@jtpio Should we postpone this to an 0.5.1? This could be done in a backward compatible way.

@jtpio
Copy link
Member

jtpio commented Jul 31, 2023

Should we postpone this to an 0.5.1? This could be done in a backward compatible way.

Probably it would be fine yes. This could be added as configurable options to keep the same defaults as in 0.5.0 but let users change them if needed (and mentioned in the docs).

@martinRenou
Copy link
Member Author

Do we actually need to make it configurable? If only fontawesome is the issue, Voila could ship its version of fontawesome in the static folder (maybe done at build time and not committed in the repo), similar to what we do for https://github.com/voila-dashboards/voila/blob/main/hatch_build.py#L12

@trungleduc
Copy link
Member

FYI I'm addressing #846 (comment)

@martinRenou
Copy link
Member Author

FYI I'm addressing #846 (comment)

Thanks! Wondering if that would fix #516

@trungleduc
Copy link
Member

FYI I'm addressing #846 (comment)

Thanks! Wondering if that would fix #516

I will investigate it.

@martinRenou
Copy link
Member Author

0.5.0b0 is out https://pypi.org/project/voila/0.5.0b0

@martinRenou martinRenou unpinned this issue Aug 3, 2023
@jtpio jtpio pinned this issue Dec 7, 2023
@jtpio
Copy link
Member

jtpio commented Dec 7, 2023

Closing as 0.5.0 has been released: https://github.com/voila-dashboards/voila/releases/tag/v0.5.0

@jtpio jtpio closed this as completed Dec 7, 2023
@jtpio jtpio unpinned this issue Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Release plan
Projects
None yet
Development

No branches or pull requests

5 participants