oVirt 4.1.0 beta2 merge / branch / tag / bugzilla reminder
All stable branch maintainers, please make sure to merge all relevant open bugs until Wednesday December 21st morning 11:00 AM TLV time (10:00 AM CET). In order to stabilize the build and allow to prepare jenkins on time, 4.1 branches need to be created before or on Monday Dec 19th. oVirt engine will be branched on Monday Dec 19th at 11:00 AM TLV time (10:00 AM CET). This build is also marking the string freeze milestone. After this build please avoid to push new strings to be translated to allow translators to complete translations for RC. For each package that need to be built (i.e oVirt product) please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the final version of the package you're building (e.g. for ovirt-engine, tag: ovirt-engine-4.1.0_beta2, tr: 4.1.0) A list of bugs that require attention is here: https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.1.0... -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
A friendly reminder about the planned build of oVirt 4.1 beta2. For ovirt-engine, build will happen from the ovirt-engine-4.1 branch created this morning. On Mon, Dec 12, 2016 at 3:41 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
All stable branch maintainers, please make sure to merge all relevant open bugs until Wednesday December 21st morning 11:00 AM TLV time (10:00 AM CET).
In order to stabilize the build and allow to prepare jenkins on time, 4.1 branches need to be created before or on Monday Dec 19th.
oVirt engine will be branched on Monday Dec 19th at 11:00 AM TLV time (10:00 AM CET).
This build is also marking the string freeze milestone. After this build please avoid to push new strings to be translated to allow translators to complete translations for RC.
For each package that need to be built (i.e oVirt product) please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the final version of the package you're building (e.g. for ovirt-engine, tag: ovirt-engine-4.1.0_beta2, tr: 4.1.0)
A list of bugs that require attention is here: https://bugzilla.redhat.com/buglist.cgi?quicksearch= target_milestone%3A4.1.0-beta%20target_release%3A---% 20status%3Amodified%2Cpost
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
participants (1)
-
Sandro Bonazzola