Michael Burns has posted comments on this change. Change subject: build: ovirt-release-10 ......................................................................
Patch Set 2: Why not just deliver 3.3.2 to the stable repository? Adding a separate location seems wrong (especially in this type of release). How does someone get the 3.3.2 release if they're already running 3.3.1? Current process (before this change) would be yum update then engine-setup. This seems to add a new step: get the new ovirt-release. You could release ovirt-release to the current stable repo, but then everyone would still automatically get the upgrade to 3.3.2. -- To view, visit http://gerrit.ovirt.org/22553 To unsubscribe, visit http://gerrit.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: If458f108384e7d2ed9520706d7224fe450643e73 Gerrit-PatchSet: 2 Gerrit-Project: ovirt-release Gerrit-Branch: master Gerrit-Owner: Sandro Bonazzola <[email protected]> Gerrit-Reviewer: Alon Bar-Lev <[email protected]> Gerrit-Reviewer: Dan Kenigsberg <[email protected]> Gerrit-Reviewer: David Caro <[email protected]> Gerrit-Reviewer: Doron Fediuck <[email protected]> Gerrit-Reviewer: Eyal Edri <[email protected]> Gerrit-Reviewer: Kiril Nesenko <[email protected]> Gerrit-Reviewer: Michael Burns <[email protected]> Gerrit-Reviewer: Ofer Schreiber <[email protected]> Gerrit-Reviewer: Sandro Bonazzola <[email protected]> Gerrit-Reviewer: oVirt Jenkins CI Server Gerrit-HasComments: No _______________________________________________ Engine-patches mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/engine-patches
