Fwd: Automated builds and releases
--TxukmIqg3MmZ0Kmh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
----- Forwarded message from David Caro <dcaroest(a)redhat.com> -----
From: David Caro <dcaroest(a)redhat.com>
To: devel(a)ovirt.org
Date: Fri, 5 Jun 2015 14:06:25 +0200
Subject: Automated builds and releases
User-Agent: Mutt/1.5.22.1 (2013-10-16)
=20
=20
Hi everyone!
=20
=20
In an effort to improve the project workflow and ease the maintenance and
improve the quality of the project releases I want to propose start worki=
ng
towards automated builds and releases, the main ideas are the
following:
=20
=20
* Stop building differently for release and non-release:
- Building only once, testing what you build and release what you test
- Don't use two different version strings, one for testing and one for
release
=20
* Automate the build process, and the release process, directly getting t=
he
code from the repos (no manual build tarballs)
=20
* Adopt semantic versioning, it's a lot more meaningful than the current =
scheme
and fits very well with the above points
=20
=20
=20
This will ease and lower the maintenance and the extra work required by
maintainers, release engineers (sandro) and infra itself by making releas=
es as
easy as hitting a button at any time. That will allow us to lower the
time
features and fixes get to the users, and deliver packages and builds that=
have
passed through all the tests we have, instead of rebuilding on
another en=
v, at
another time, by someone else, and passing only manual testing.
=20
=20
wdyt?
=20
=20
--=20
David Caro
=20
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
=20
Tel.: +420 532 294 605
Email: dcaro(a)redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
----- End forwarded message -----
--=20
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605
Email: dcaro(a)redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
--TxukmIqg3MmZ0Kmh
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJVcb6KAAoJEEBxx+HSYmnDXpwH+wXoAeY/0DomiTpwBmo7WIxN
lbM1YOpUJyUN91r8DiwSQ50ZPbagZup8kwFsExbLn1tUjg20h8Cv0O53AgoPNV7v
OB2dXja8lkWjpln9LaweTtbDQZvm+4YQaxuYHe+zaz62nL1Eser5IPAIlmMW5Zl7
8rLLdpoh7IN9mI3j7PjLRyqWvq9ZQYnCLOLbndmKDUqKMOR5DbFfa9Nw3rAEweYR
6MYDS8l3UvlARP64yl2AZ7e7vIhEkRr0WC/Tx3hr47m7LGT1icWaOdLCSARgA5He
ZVeRdm8Nn8ZAIiIyeanXFRIcbP8pNFBJh2CiCSRu2rUyDUEED+WNO1EtZQM7CcU=
=dvp2
-----END PGP SIGNATURE-----
--TxukmIqg3MmZ0Kmh--
Attachments:
- attachment.bin (multipart/signed — 2.6 KB)