Register the latest release at General

[ablaom]

Despite the existence of a tag 0.6.1, this version is not actually registered at General:

https://github.com/JuliaRegistries/General/blob/master/O/OneRule/Versions.toml

To registry a new release see this help page.

[roland-KA]

Thanks for the hint!

The registration bot tries to be more intelligent as he actually is (JuliaRegistries/General#145006). He states, having detected some breaking changes (as it seems just from the change in the version number), but there aren't any.

I've tried to advance the PR and overcome this obstacle. But it doesn't work. I've added a comment in the release notes (as recommended) with the key words "breaking changes", but it doesn't help.

I'm stuck. I don't know how to register this version.

[ablaom]

Gosh, how frustrating. Are you using @JuliaRegistrator or JuliaHub?

[JuliaRegistrator]

Error while trying to register: Action not recognized: or

[JuliaRegistrator]

Error while trying to register: Action not recognized: or

[ablaom]

You can ignore those two above. Well, they tell us you do have JuliaRegistrator installed. This is how I make updates. If you haven't already, try registering by posting in any issue comment (here for example) what you see in that example. If you already tried this, point me to the comment, and I'll take a look.

[roland-KA]

I've added now a comment asking for help in the PR for the registration. Apart from that I've posted a message in the #pkg-registration-Slack-channel (es they recommend on the Registry web page). Hope they will solve it.

[roland-KA]

Finally I've managed to register that release! But I think that I've put now more effort in the registering process than in implementing and testing that release 🙃.

In the meantime I have the impression that the Julia ecosystem has gotten too complicated in comparison to others like e.g. Rust. Especially the tooling around the language (e.g. package management, registration, documentation via Documenter etc.) are way too complex for newcomers or on-and-off users like me. Just one example is the process in Rust for the first registration of a crate and the release of new versions: https://doc.rust-lang.org/cargo/reference/publishing.html. It's straightforward and well supported by integrated tools.

[ablaom]

Thanks @roland-KA for persisting. It sounds like this was a frustrating experience. I can imagine the tooling is not easy for irregular users. I'm not involved with the tooling side of Julia. Maybe you share your feedback on the #pkg-dev slack channel.

For sustainability of your package going forward, you may want to consider transferring ownership to an org like JuliaAI, which hosts most of the MLJ ecosystem. For example, in the current scenario I could have stepped in to register your package, as one of the org owners. I would immediately make you an administrator of the repo. Only you and org owners would have access by default. There are currently four owners; see here. JuliaAI falls under these rules of governance. We are all spread thin, so this is no guarantee of long term survival, but the chances are better, I think.

[roland-KA]

Hi @ablaom, that's a good idea and would make situations like this easier to handle. What do I have to do to transfer the ownership to JuliaAI?

[ablaom]

You may be able to do this yourself, as you are already a JuliaAI member. Got to Settings, srcroll down to the end ("Danger Zone") and change the "Ownership" to JuliaAI. Otherwise, make me an administrator of your package and I will do it.

[ablaom]

If you do it yourself, ping me and I will make sure you are still an administrator.

[roland-KA]

Hi @ablaom, I've transferred ownership now to JuliaAI. But I have lost administrative rights on the repo. Could you grant me these rights back?

[ablaom]

Thanks for making the transfer. You should have full admin access now.

[roland-KA]

I've just had a look on it. It works 👍. Thanks!