Closed IshaanDesai closed 2 years ago
The easiest way would be to install the Registrator bot in this Repository, then we would only have to tag the bot in a github issue and the bot would automatically add the Package to the Registry within a few days. New releases would also be done this way in combination with the TagBot We should change the version of the Package in the Project.toml Should we do this before the next milestone with a pre-release version, or only with the first release?
A few more comments on the above mentioned bots.
The Registrator bot takes the version number from the [Project.toml] and opens a pull request at the Julia General Registry when instructed by a comment (@JuliaRegistrator register
) on the commit/branch that we want to release. This is an example. A moderator will have a look at it and maybe leave some comments if we should change something. Otherwise, the process doesn't require input from our side.
The TagBot automate the process of a github release every time the Registrator bot is called. And is also able to generate changelogs with the new release.
Okay, the whole strategy looks very streamlined. Once we have sorted out all the issues that we want to address in the upcoming release, lets do a Pre-release and try out this whole workflow. Once we know it works we can deploy it on the actual release v2.4.0.0
Done in fist experimental release https://github.com/precice/PreCICE.jl/releases/tag/v0.0.1
The julia-bindings should be added to the Julia General Registry so that they can be installed using the
add
command usingPkg
.