I will tag the first release candidate, as already mentioned. I don't like
the repo being filled up with tags, so if we are going to use them I'll be
keeping them to a minimum. Having tags permanently in there for something
that served a purpose for one week only seems horrible to me.
Having
Le jeudi 14 mai 2020 à 18:51 +0200, 'Bill Hart' via sage-devel a
écrit :
> The (latest) commit c6319d1d36248f2fc699e833ab2f6fa70d21e906 in the
> official Flint repository [1] is flint-2.6.0-alpha1.
You could tag it : that would be clearer.
Something like "git tag 2.6.0-alpha1" then "git push
Hi all,
The (latest) commit c6319d1d36248f2fc699e833ab2f6fa70d21e906 in the
official Flint repository [1] is flint-2.6.0-alpha1.
This is an opportunity for early testing and feedback before our first
official beta which will be released about Wednesday next week.
Some release tasks have not yet
