0.0.92 Release
emmaccode opened this issue · comments
0.0.92 will be addressing the shortcomings of the current workmenu and project explorer configuration, as well as focus on nuances with opening files and improvements in those aspects of Olive.
There will also be an overhaul to setup, moving the entire setup concept into session and simply making an alternate project for setups.
Finally, there will also be a consistent build_base_repl_cell that comes along with this. Whereas 0.0.91 focused on refining the back-end to some degree and polishing some aspects of the session frontend, this update will focus mostly on directories, files, and how they are managed in Olive!
0.0.91 has just merged :)
#135 has changed some things, I am closing #117 -- it will now be somewhat more along these lines, I am going to close all the issues that do not apply.
So this update is going to focus primarily on converting free mode into the norm, but also enhancing this to use more of a global Olive environment, which is still able to to load extensions and save extension settings. This also maps a pleasant avenue into 0.0.93, so I am going to go ahead and open that Release issue up after this in order to get it all planned out.
So I just completed ( I think, at least -- for now ) Session's third parser -- originally it was EzXML then it was the htmlcomponent we have used here and beyond. Compatibility will be restricted to Session 0.3.6-0.4.0 in 0.0.92.
As for the status of the update, the status above is still reflexive -- I am currently working on #113 / #112 and #135 all at the same time.
then I will take a few days to play around, need to do even more work to ToolipsSession -- always. Next week -- 0.0.92 along with the first Gattino release (excitement!).
done ! awesome !
I am just finishing some final small things and tweaks for this next version. Also rewriting a lot of the README :)
It is looking quite nice.
@JuliaRegistrator register
Registration pull request created: JuliaRegistries/General/97253
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register
Release notes:
## Breaking changes
- blah
To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.0.92 -m "<description of version>" 56519b747736cad4b6382b51477054e0b6de956c
git push origin v0.0.92
@JuliaRegistrator register
Registration pull request updated: JuliaRegistries/General/97253
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register
Release notes:
## Breaking changes
- blah
To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.0.92 -m "<description of version>" 3c3f9e2ac1cda9445bae4ae7357aa4223aa953ad
git push origin v0.0.92
yay ! :D 💃🏻