Buildbot notifications

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============2039931689==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig076756DA4F6838B03E8D4884"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig076756DA4F6838B03E8D4884
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear CPS developers,

as of now, the buildbot will notify this list of builders status changes
(typically from success to failure and back).
This way, developers will be informed of current problems that may
impact their work or bleeding-edge based deployments, and get a notice
when situation is back to normal.
I'll do a voluntary failure and fix in a few minutes to test the
notification itself.
=20
Of course, this also serves the purpose of fixing the problems as soon
as they occur. That's usually easier than a month later.

We considered also sending these notifications to the code mailing list,
but decided that they would be unnoticed among the changesets and trac
notifications. Build failures are supposed not to happen that often, but
of course the purpose of using a tool such as buildbot is to perform the
extensive testing that would not be realistic in the typical developer
workflow, so they will happen.

All of this is still in progress and a bit experimental, we'll see what
to do if people here find that this generates too much traffic.

Regards,

--=20
Georges Racinet, http://www.racinet.fr
Zope/CPS expertise, assistance & development
GPG: 0x4862FFF7 identi.ca & twitter: gracinet



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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPMSDEAAoJEOAffZJiF+Z4Px4IAJr/w/0gFpFlO6Us0gat8rWQ
uNrqOKIY2deyFEFR/PqhfqG6c+zm8aPg4gfhN+WgIZeknpPquetAziXqVEHAfnrK
mB0p/eUCXJYn16ttBE6531FJAlKLZ3nXyE0yOvKou0eJ9TZu8MRthRq8YoFOvGDO
2IRWpV+M7tsoVH3G9X4cuneZRblgVJvES+WgQsMll5OyiETgiYp5aETIWJ+7+7F1
Q+l2Ef4hDayKFy3Wz/TYIxp9MfQtfWnu8Zh9qv5jKHgC99GEql/mGM8G8SG0M1kN
TeoXMwIPk9Tbsjo62mOGVJ4hI2VK/5D589hzXfWR3kpdriw4LEK2yw8ZXaKIoPc=
=vTwR
-----END PGP SIGNATURE-----

--------------enig076756DA4F6838B03E8D4884--


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

_______________________________________________
cps-devel mailing list
http://lists.cps-cms.org/listinfo/cps-devel

--===============2039931689==--