Rise: roadmap

Created on 5 Jul 2019 · 28Comments · Source: damianavila/RISE

because things tend to have become a bit shuffled up recently, here's a quick braindump

5.5

I have issued 5.5.1 yesterday as a stable release
it's on branch maint-5.5
the change is only that hotfix for #375

5.6

in essence this is about reveal-3.8.0
I just issued a dev release numbered 5.6.0-dev4
this is on branch maint-5.6
it's primarily 5.6.0-dev3 plus a few recent small improvements
changelog is up-to-date (in the branch at least)

There are also 2 rather important changes in the git tree on top of 5.6:

branch `split-rise-reveal` is about #490

it does not come with many changes in the code itself
but building and packaging must be double-checked because that can easily have suffered in the move
also the way the rise-reveal npm package exposes its contents - namely through an export subdir is maybe not exactly elegant; later on I read about webpack that uses the dist/ convention instead, it's the same intention, but if anyone has something to say about my choice it would be good to speak up soon :)

branch `jlab-redeux` is about the jupyterlab extension

nothing much is working at this point but we start to understand how we'd fit into the landscape
this branch right now sits on top of the split-rise-reveal one, because it leverages of course the split

In terms of numbering and releasing, I can see several options, but they all start with:

STEP 1
issuing 5.6.0 as essentially 5.6.0-dev4 + bugfixes if needed (I'm quite happy with it at this point, but may have not tested the complete feature set)

Let me remind that everyone can give this a try with

pip install -U --pre rise

and reports - bug reports or OK reports - are always welcome :)

EDIT 2019/11: release 5.6 is now officially published, the --pre option is no longer required

discussion

Source

parmentelat

❤1

Most helpful comment

hi Damian, I just invited you

parmentelat on 29 Oct 2020

😄1 👍1

All 28 comments

5.5

Perfect! Thanks! I have redirected the root of the docs page to the maint-5.5 branch for now... so we can show the proper changelog.
Additionally, I can confirm conda packages are available trough conda-forge as well.

damianavila on 7 Jul 2019

STEP 1
issuing 5.6.0 as essentially 5.6.0-dev4 + bugfixes if needed (I'm quite happy with it at this point, but may have not tested the complete feature set)

I agree with that, let's have the beta out there for 2 weeks. So we give people (and me :wink:) time to test and play with it (reveal-3.8 is a big change, so let's give the bugs enough time to surface). Then, we can release it if we do not have any blocker.

damianavila on 7 Jul 2019

but building and packaging must be double-checked because that can easily have suffered in the move
also the way the rise-reveal npm package exposes its contents - namely through an export subdir is maybe not exactly elegant; later on I read about webpack that uses the dist/ convention instead, it's the same intention, but if anyone has something to say about my choice it would be good to speak up soon :)

Now I have a PR to review #490 :wink: so I will provide my feedback on it pretty soon.

damianavila on 7 Jul 2019

nothing much is working at this point but we start to understand how we'd fit into the landscape
this branch right now sits on top of the split-rise-reveal one, because it leverages of course the split

Great, it is the next big thing... we should discuss later how we are versioning classic and lab extensions. but let's focus first on making the labextension a real thing!

damianavila on 7 Jul 2019

RISE 5.6.0 is available in PyPI (https://pypi.org/project/rise/5.6.0/) and it is being built in conda-forge: https://github.com/conda-forge/rise-feedstock/pull/26.

After confirming everything is OK, I will be removing the maint-5.5 branch and reporting the release on the corresponding issues.

Finally, I will make a blog post with the ANN.

cc @parmentelat

damianavila on 13 Nov 2019

short update

I have made a pass to publish 5.7.0-dev releases; it took an awkward few screwed up attempts to get everything right wrt github/readthedocs/pypi with the new sources layout, but I'm rather happy with the result (including proper markdown rendering on pypi) , so we can now instruct adventurous people to install that 5.7 release using the usual

pip install -U --pre rise

I have tidied up the master branch as bast I could, at that point I believe all the changes made in maintenance branches are in there

as a side note @damianavila, I don't seem to have management rights on pypi; I can publish, but I cannot clean up behind me, so I'd appreciate if you could spend 5 minutes removing useless dev releases there (or give me management access if you find out how to do that :)

also @damianavila, would you mind writing down a short update on your end regarding jlab ?

parmentelat on 4 Jun 2020

I have tidied up the master branch as bast I could, at that point I believe all the changes made in maintenance branches are in there

Thanks for all that work! Do you think we should release 5.7.0 anytime soon? I see you released several dev versions so maybe it is a good time now...

as a side note @damianavila, I don't seem to have management rights on pypi; I can publish, but I cannot clean up behind me, so I'd appreciate if you could spend 5 minutes removing useless dev releases there (or give me management access if you find out how to do that :)

That's weird... You have a maintainer role there... that, it seems it is not enough to remove package. So I made you an owner as well, you should be able to remove packages now. Btw, I am not sure if we want to remove dev packages... probably yes. If you want to try your new powers, that would be nice to check everything is set up properly.

also @damianavila, would you mind writing down a short update on your end regarding jlab ?

I will try to do that this weekend on the corresponding issue, but I will leave a link here as well.

damianavila on 11 Jun 2020

yes I think we should issue a 5.7 as soon as it has gone through your testing, as it is mostly equivalent to 5.6 in terms of functionality but has the new sources layout in place

permissions all right and cleanup done; thanks
I am keeping only the last dev version online - we still have tags in the git repo for those dev versions

parmentelat on 12 Jun 2020

yes I think we should issue a 5.7 as soon as it has gone through your testing, as it is mostly equivalent to 5.6 in terms of functionality but has the new sources layout in place

OK, planning to make that release toward the end on Jun.

permissions all right and cleanup done; thanks

Wonderful

I am keeping only the last dev version online - we still have tags in the git repo for those dev versions

Make sense!

damianavila on 18 Jun 2020

just released 5.7 on pypi

@damianavila please push onto conda if needed

parmentelat on 24 Oct 2020

Perfect, I will make the conda packaging tomorrow!
Thanks @parmentelat!

damianavila on 24 Oct 2020

It doesn't seem like there's a corresponding tag for the release?

dhirschfeld on 25 Oct 2020

oops sorry, forgot to push the tag, it's done now

parmentelat on 25 Oct 2020

👍1

Perfect, I will make the conda packaging tomorrow!

Thanks to conda-forge, it seems we had a bot doing the whole conda stuff for us: https://github.com/conda-forge/rise-feedstock/pull/32.

And I can see the package here: https://anaconda.org/conda-forge/rise/files?version=5.7.0 which is lovely :wink: