|
From: | Phil Holmes |
Subject: | Re: 2.14.2 |
Date: | Fri, 15 Jul 2011 14:24:41 +0100 |
Am 14.07.2011 14:53, schrieb Carl Sorensen:Well, I think this is imporant, because if I can verify an issue in a development version it really doesn't guarantee that it will also work with the backport. So you really should verify against both versions.On 7/14/11 6:23 AM, "Urs Liska"<address@hidden> wrote:Hi guys, as you may have noticed I gained some activity again lately.Glad to have you back!I think I have to apologize that I faded out of my Bug Squad duty silently half a year ago.Apology accepted.This as a general remark, now to my current question: When do you expect 2.14.2 to be released?I think it's ready when Graham gets to it. I expect it soon.ATM there are many issues to verify that are marked as fixed_2_14_2. So before this version is released the issues can't be verified.I think that in the past we have marked it as verified when fixed in the development version, and not waited for the backported version to be released. But I think the policy you are proposing is better.Good idea. I just started with the two issues I had looked at today before I stopped because of the missing 2.14.2Perhaps when it's verified in one of the versions, a tag indicating that should be added: verified_2_15_5. Then when it's been verified in bothversions, the verified_2_15_5 tag is removed, and status is set to Verified.Best UrsThanks, Carl
I agree with Urs. If it's marked backported to a 2.14 release, it can't be verified until verified on that release too.
-- Phil Holmes Bug Squad
[Prev in Thread] | Current Thread | [Next in Thread] |