On Saturday, December 28, 2019 at 3:56:37 AM UTC-5, Giovanni Mascellani wrote: > > > on my dashboard. This is as simple as using these commands each time you > want to publish a new release: > > git commit -m'Release version 0.1234.' > git tag v0.1234 > git push > git push --tags > > The tags will be published on GitHub[1] and will be available for > automatically knowing which versions are available and how to get a > specific version. > > OK, I can add this to my release process for the metamath program source code.
Currently I am the only maintainer of the source code (m*,c,m*.h), and I don't publish intermediate versions of the program without incrementing the version number. However, others may make small changes to configure.ac etc. that aren't related to the code and don't cause the version number to change. Should these be re-tagged with the same version number? Or not tagged at all, and just wait for the next real version? -- You received this message because you are subscribed to the Google Groups "Metamath" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/metamath/5105ef13-0fa2-4391-bde6-16dae9636fc2%40googlegroups.com.
