Question about API stability of autoconf-archive

Hey,

We’re thinking about eliminating gnome-common[1] in favour of
recommending autoconf-archive macros instead. This would simplify the
build system for a lot of GNOME modules.

We have one important question: what’s the API stability policy for
autoconf-archive macros? Once a macro is in an autoconf-archive release,
is it committed to API stability for ever, or is it free to break its
API whenever it likes (subject to updating #serial)?

Thanks,
Philip

[1]: https://git.gnome.org/browse/gnome-common

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iF4EABEKAAYFAlTGGgYACgkQ8JQuiUsur6CakAEAiz64zzN+GavdyNshfY7wwfsW
0Thc3TP/za9suJP3yxMBAIiRCouhqVlmredG96NQCSdAQm46h/ofAkwYj8ATT7yA
=flI/
-----END PGP SIGNATURE-----