-
Notifications
You must be signed in to change notification settings - Fork 5
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
Version 0.2.0 is not in General
registry
#8
Comments
This project has not been actively maintained. Would you want to make an update to current Julia (note that it still uses Would that work with you? |
Sure. I will get back to it once I figure out my need. |
I ended up doing something different that no longer requires taking a dependency here. The very old v0.1.1 release of this package is still working fine on Julia v1.8 due to its simplicity. However, the inconsistency between GitHub release and |
OK - thanks. |
JuliaRegistries/General#52720 closed without being merged. Issuing a release from 9136dca should be enough to trigger it. |
@bkamins if you don't want to maintain this (believe me, I more than understand why you might not!) you might consider whether you'd like to transfer this to JuliaArrays? (Many people have merge privileges there and you would no longer be responsible.) If you want to do the transfer, I can grant you privileges. Ping me on slack if I don't notice a reply here. |
I think it is a good idea. I wanted this package to have limited functionality. Recently, it seems that people started using it and are raising new issues that are hard for me to judge, especially against the functionality of StaticArrays.jl. So, it is probably good to move it to a more curated place with people who better understand the direction of the ecosystem's development. In short: can you please give me rights to transfer? Thank you! |
I sent an invitation. |
Thank you! - The repo is now transferred. |
I notice that the PR for v0.2.0 release was never merged in the
General
registry and got closed automatically. There seems to be some confusion regarding the release process for that. I suspect that the GitHub release was not triggered from the TagBot but come from a manual git tag.The text was updated successfully, but these errors were encountered: