On 09/25/2013 07:19 AM, Itamar Heim wrote:
On 09/25/2013 10:40 AM, Ofer Schreiber wrote:
Hey,
As you may know, we're planning to release oVirt 3.3.0.1 soon.
I've created a tracker bug
(https://bugzilla.redhat.com/show_bug.cgi?id=1011800) and a git branch
(ovirt-engine-3.3.0.1, based on 3.3.0) for this release.
If you're working on a really urgent bug, please notify me or Mike, so
it will be included in next version, otherwise, most issues will be
included in 3.3.1 which will be based on the ovirt-engine-3.3 branch.
Please don't merge anything into 3.3.0.1 without consulting.
If all those branches and releases makes you dizzy, ping me on IRC and
I'll try to clear it out.
Thanks,
Ofer Schreiber
also, please make sure any bug going to a stable branch has a bug-url,
to allow decent release notes on stable releases.
Thanks,
Itamar
I assume that it goes without saying (but I'll say it anyway) that
patches should go to master before going to any release specific branch.
Mike
_______________________________________________
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
