Re: [ovirt-devel] Automated builds and releases

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?

-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGcBAEBCAAGBQJVcZpWAAoJEAq0kGAWDrql3PcL/jRFRr+dg7gpSFYM9jWWMb06 o4DOfjRmDga0YCPLoHQk1/tZwAHkJqMLSrkrkWk2RWYK9dR0ckaWJ5CIA8OuNA5g et+KCVpVnC5FYwbR1Joo5I3ODgSkPONDsE9JdBn1ClT0JRs4U81Wb5ludZNYdtBo Zxu9va86mPIJNd2B6RDc990XOd0HvTTGxfYtbmiBCwGxKlS6imNkTPUW6HzCVC2w ofL4qLGy9JiV0bHKjdOX1K713BDtqtTXTtiME/tvUqhFJRWSQFdP182ftCEMa/xF I5eGCTc17JDKg3PHbufNCdmQevXuk0PpeFX2QbgRxuGfqkL04RsDW8iTyMfo9men /FImHViJhWkum5xWCZJiNDIPvoNkdKcQndu6J6jWbSuEfrUTPG99etb3VL9/dz4L XM8upOrNnpcVkL1x3SWFUYLs739LEJEaNlZ0R3hWtUWv1D8iu1IjQ2xxWbpjcOAv ccvwyXGV12Uon5F8DWb24y6CQb53WhsBVKY5blYH+Q== =f8Ru -----END PGP SIGNATURE-----