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
signature.asc
Description: OpenPGP digital signature
_______________________________________________ help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
