Target state of gnome-build-meta

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============9171655879310744151==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline



--===============9171655879310744151==
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="nd63lbyUKWVlV2P1kVKSB4VcSxVyBh4iR"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--nd63lbyUKWVlV2P1kVKSB4VcSxVyBh4iR
Content-Type: multipart/mixed; boundary="BT22Qosqlxchcjq2G0D2A1y8lZlNPhILS";
 protected-headers="v1"
From: Karl-Philipp Richter <[email protected]>
To: [email protected]
Message-ID: <[email protected]>
Subject: Target state of gnome-build-meta

--BT22Qosqlxchcjq2G0D2A1y8lZlNPhILS
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable

Hi,
I'm not involved in GNOME development so far, however I use GNOME for
years and love to build and contribute to FLOSS. Thank you for it!

Over the years I had my troubles building GNOME application from source
which I did for various reason, e.g. investigate presence of an issue in
the most recent version, out of curiosity, for fun and more. I'm very
pleased with the creation of gnome-build-meta, the progress of the
migration to GitLab and the use of the CI there.

I'm investigating unused potential which I see in the current processes
and seeking to prepare an overview as basis for a discussion. In order
to avoid unnecessary work I'm looking for an eventual definite statement
about the target state of
[gnome-build-meta](https://gitlab.gnome.org/krichter/gnome-build-meta)
in terms of stability of the master branch. If there's one defined, are
build failure allowed in this target state (no matter how it looks now)?
Are merge requests allowed to be merged before CI passed?

-Kalle


--BT22Qosqlxchcjq2G0D2A1y8lZlNPhILS--

--nd63lbyUKWVlV2P1kVKSB4VcSxVyBh4iR
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEE/HzQfDL1JMOgMQM+Zp0onx4ntkYFAlzJl9wACgkQZp0onx4n
tkYrSgf9HMIYjoeI6Yo6aU1l8OPIbatMtfND5swVX+2zdTf2KTeCC3uNQtM6pzq2
flROATsB6wNemnErdPq2VQddPBrcYi8nTHpsHaoPBlNUXr4MGO/RDhyF5HxPlMyb
5Y4cfmsOIL9NjgkZwThHfEqpDTOFylUzmp+oaCgaXmrUQjlG9lDGlxhqix3RrJFZ
sKb5OybtT0HZbu3vWZ+SoBkKe6d63CdgS+TcLybBn7NHAYvVlyfV8yyTHJ1S9r+x
tky0+bT9WKXNcVBHuG1sBwZiWOhE6xOYxtH9QVsJkwh7elchI3Oj+4QBG2F7OhQu
7Fl0na5Em86ZVXALaBJ1HVYNV+OWpA==
=N/PN
-----END PGP SIGNATURE-----

--nd63lbyUKWVlV2P1kVKSB4VcSxVyBh4iR--

--===============9171655879310744151==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
gnome-devel-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/gnome-devel-list

--===============9171655879310744151==--