Switching package registration systems soon

Is this a good example of the Registrator workflow, just so I don’t misunderstand the stuff. I couldn’t find a complete description of the workflow.

Creating a new package:

(1) Create a new package using these instructions in the pkg docs.

(2) Work on the code until you are satisfied, and do commits as you like.

(3) Change the version number in the Project.toml file to one you like, or keep it. Then make a commit and comment on that one with “@JuliaRegistrator register()”. Wait until the maintainer accepts the pull request. (Here there are options using PRs and issues too).

(4) Optionally: Tag a release on github that matches your version number in Project.toml file.

Creating a new version release of an existing package by repeating step 3 and 4.

Is this a good way to do it? Does this mean that the maintainer of General will have to accept the PR for each new version release too, not only new packages? Thanks for feedback.

1 Like