Open junyuan-chen opened 1 year ago
This project has not been actively maintained. Would you want to make an update to current Julia (note that it still uses REQUIRE
which is long removed)? If so can you please make a PR and I will review it, merge and make a new release.
In this way we will be sure that the released version meets your needs.
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 General
registry version is still there. So, I guess this issue will serve as a reminder. But, there is no urgent need to make changes at this moment.
OK - thanks.
https://github.com/JuliaRegistries/General/pull/52720 closed without being merged. Issuing a release from 9136dcad71f6e47878ced51f6ade79e340a2f878 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.