We added it to allow testers to take bugs prior to the alpha.

Target release should contain the build used to move it to testers, but in this case we are before the alpha and there is no build.

YANIV LAVI (YANIV DARY)
SENIOR TECHNICAL PRODUCT MANAGER
Red Hat Israel Ltd.
34 Jerusalem Road, Building A, 1st floor
Ra'anana, Israel 4350109
ylavi@redhat.com    T: +972-9-7692306/8272306     F: +972-9-7692223    IM: ylavi
TRIED. TESTED. TRUSTED.
@redhatnews   Red Hat   Red Hat

On Mon, Aug 28, 2017 at 11:35 AM, Yaniv Kaul <ykaul@redhat.com> wrote:

On Mon, Aug 28, 2017 at 11:21 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:

Hi,

not sure who added "pre-alpha" release to bugzilla, but "pre-alpha" is not a release so it's meaningless.

Please note we have 52 bugs on engine with that release  set: https://bugzilla.redhat.com/buglist.cgi?target_release=pre-alpha&product=ovirt-engine

There are more on other products, such as VDSM (https://bugzilla.redhat.com/buglist.cgi?list_id=7780186&product=vdsm&target_release=pre-alpha ).

Indeed no idea who added it and why.

All are closed, btw.

Y.

 

Please ensure your bugs have a valid target release (in this case I guess 4.2.0) so we can get rid of that meaningless release target.

Thanks,

--

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA

TRIED. TESTED. TRUSTED.

_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel