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 said that, I should clean up more dead branches in my repo. On Thursday, 21 May 2020 13:30:49 UTC+2, Julien Puydt wrote: > > 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 --tags" is enough. > That way the repository will document which tag is that alpha1, and > github will make tarballs automatically. > > Cheers, > > JP > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/bf7e3148-b32b-4019-b720-058ff3acb242%40googlegroups.com.
