Re: RFC: creating a bison-announce list
Simon Richter <[email protected]>
| Newsgroups | gmane.comp.parsers.bison.general |
|---|---|
| Message-ID | <[email protected]> |
Hi Akim, On 06.01.19 09:10, Akim Demaille wrote: > It has been asked to explicitly mark releases on git, so that CIs can trigger builds automatically with these releases. This is already the case: tags mark releases (betas and stable). Will it be sufficient to test betas with existing projects? IIRC the problem was that broken use cases were detected only after releases had been gone out, as people upgraded. The suggestion was to have "release candidate" tags as well that are basically a machine readable form of the announcement mail that asks if there are any showstoppers for doing a release. > If monitoring tags is inconvenient, Monitoring tags is just about the only thing that is convenient in modern CI systems. Simon _______________________________________________ [email protected] https://lists.gnu.org/mailman/listinfo/help-bison
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEtjuqOJSXmNjSiX3Tfr04e7CZCBEFAlwyc4YACgkQfr04e7CZ CBFKUAf/Y+ow6gOKffqAZ2rL2r8QN4BdXc0jyceKHQSFdm9i6NMSeGw2OxHzbOHb dX7ZH4tyCWrluEqts+sgPBa65b5dNMgEEtGI1xjA7wduEkjcJdo5HAVm2BIiuoQj 2JS5Pcek7vBqNENpjK7Ru9MCgQWaAytl7chReGgMSG2xfhWEtYMlRuDmvgJo1Oie ircVKSSOWJtxNuym7xMHbCcFkg6tRpqN5liDyuxGZgqfg6BdaRFD7eapokmmrkI9 Bl2gEFGq5/tfaxFfFtFEG4a5e9OQr2LKEYZzPn1mvAxNAw9U9wM17zNFw5/+ZSuk Gqx8umClQkhnsxcPAC7WToRHMRHqOw== =XRto -----END PGP SIGNATURE-----