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

Transitioning from Manifolds.jl #7

Open
kellertuer opened this issue Sep 16, 2024 · 0 comments · May be fixed by #12
Open

Transitioning from Manifolds.jl #7

kellertuer opened this issue Sep 16, 2024 · 0 comments · May be fixed by #12

Comments

@kellertuer
Copy link
Member

@Affie wrote

Ok, no breaking release, but let's face it: people will have to adapt from Manifolds.jl to LieGroups.jl. I call that breaking even if it is not.

Yes please make it as easy as possible to upgrade, I understand some things will break, but even an error("deprecated, please use...) goes a long way. The v0.9 to v0.10 upgrade affects about 8 packages.

I was not aware that it is 8 packages. You can also stay on Manifolds.jl 0.10 for a while (0.11 in my mind for now just removes Lie groups then). Keep in mind that this package will also take a long long long while in my mind for now.
I am learning this along the way, try to document all functions with formulae, but I also have this thing called “semester”, lectures, supervision,... so I am not sure how long this package here takes until its first release – maybe Christmas? Easter? Something like that

The idea for transitioning to this package, for now I document all new functions (and where they come from) in the NEWS.md file (cf. https://github.com/JuliaManifolds/LieGroups.jl/blob/kellertuer/Intro/NEWS.md). I could start a branch of Manifold.jl and add a deprecation to every function I move, but that would probably double development time – and be a very tedious and boring coding task especially for all functions that really just move.

I might write a tutorial for moving to cover the core parts that change and how to adapt. But feel free to propose what to do best to move.
And again, this is. probably not urgent, I would really not expect this to be any close to completion before Christmas – even starting this now was not my plan but maybe somewhen in a year originally, though I had the idea in a few issues prssibly about two years back, that “someone should do this”, just that there was no one.

@kellertuer kellertuer transferred this issue from another repository Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant