On 06.05.2014 21:33, tmodes wrote:
> Tried to fix in changeset 1df056cbbdd8 in default branch.
>
> If there is a confirmation, that the bug is fixed we need a decision how to proceed with 2014.0.
> If the bug is considered as critical, it needs to ported to 2014.0. This will need a new release candidate rc3.
> What is your opinion?
I'd give it a week or two more and see what else may be cropping up.
There is no reason to hasten the 2014.0 final release, we still have a
couple of months until 2015 ;)
From a supporter POV, I'd like to have a bug like this fixed, though.
On 06.05.2014 21:33, tmodes wrote:
> Tried to fix in changeset 1df056cbbdd8 in default branch.
>
> If there is a confirmation, that the bug is fixed we need a decision how to proceed with 2014.0.
> If the bug is considered as critical, it needs to ported to 2014.0. This will need a new release candidate rc3.
> What is your opinion?
I'd give it a week or two more and see what else may be cropping up.
There is no reason to hasten the 2014.0 final release, we still have a
couple of months until 2015 ;)
From a supporter POV, I'd like to have a bug like this fixed, though.
Regards
Stefan Peter