On 28/01/15 11:53, Sven Kieske wrote:
> Hi,
>
> just a quick question:
>
> Would this imply that you need to create
> separate bugs to track these "solved on master" bugs
> for the next release?
>
> So you know the fix/feature really hit's the release?
>
> Or how would you track that?
>
I w
Hi,
just a quick question:
Would this imply that you need to create
separate bugs to track these "solved on master" bugs
for the next release?
So you know the fix/feature really hit's the release?
Or how would you track that?
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministra
Il 28/01/2015 10:44, Lior Vernia ha scritto:
> Hello everyone,
>
> I wanted to suggest that we automate the change of oVirt 3.6 bug status
> from MODIFIED to ON_QA based on nightly snapshot builds.
>
> The motivation should be clear: when bugs are fixed on the master
> branch, the fix becomes rea
- Original Message -
> From: "Lior Vernia"
> To: devel@ovirt.org, in...@ovirt.org
> Sent: Wednesday, January 28, 2015 10:44:44 AM
> Subject: Move bugs to ON_QA based on snapshot builds?
>
> Hello everyone,
>
> I wanted to suggest that we automate the change of oVirt 3.6 bug status
> fr
Hello everyone,
I wanted to suggest that we automate the change of oVirt 3.6 bug status
from MODIFIED to ON_QA based on nightly snapshot builds.
The motivation should be clear: when bugs are fixed on the master
branch, the fix becomes readily available for verification as soon as
the next snapsho
