[ovirt-devel] Automated builds and releases

[David Caro]

Hi everyone!


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 working
towards automated builds and releases, the main ideas are the following:


* 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

* Automate the build process, and the release process, directly getting the
  code from the repos (no manual build tarballs)

* Adopt semantic versioning, it's a lot more meaningful than the current scheme
  and fits very well with the above points



This will ease and lower the maintenance and the extra work required by
maintainers, release engineers (sandro) and infra itself by making releases 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 env, at
another time, by someone else, and passing only manual testing.


wdyt?


-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D

Tel.: +420 532 294 605
Email: dcaro at redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20150605/6a383d3d/attachment-0001.sig>