Improve release guide

[BryanCazabonne]

The release guide could be improved by adding the following information:

• New taks -> Prerequires : (1) Generate a personnal key-ID and (2) Ask for an account on Hipparchus server
• In Generating signed artifacts, say that the whole "hipparchus-aggregator" and "hipparchus-coverage" must be removed by "right clic" and "Delete"
• Add a new section after Uploading non-maven artifacts. The name can be "Prepare the site for the release" and shall contain the operations to perform.
• Improve the "After the vote" section : (1) Create a dedicated section for tagging the version (2) Add a section for merging release-X.Y into master (3) Add a section explaining how releasing on sonatype (4) Add a section "Declare the release on Github" by adding a new release in https://github.com/Hipparchus-Math/hipparchus/releases/ and (5) Add a new section "Finalize the site after the successful vote"

[axkr]

Dependabot already creates 3.0 changes. Is this intended?

• https://github.com/axkr/symja_android_library/pull/832

[maisonobe]

No, it is not intended and indeed the dependencies reference the 3.0-SNAPSHOT version, not the upcoming final 3.0.

Edit: Scratch that, they reference 3.0. I'll have a look at it

[maisonobe]

After a quick look, I think it is due to the repositories list.

For the general public, the version is still only available in the staging repository and the latest official version in maven central is still 2.3.

For expert uses, our own repository that is triggered by the Continuous Integration framework provides all versions, even development ones. When the branch for 3.0 release was created during the release process, the maven artifacts were pushed there automatically.

So I guess you reference our repository in Symja.