Yes, I agree. The cleanup is what I'm trying to do :-D
Mad? Possibly, but it's one of those things where one has to throw the
heart beyond the obstacle, or it won't get done ever.
Cheers
Andrea
Cheers
Andrea
Il dom 10 mar 2019, 15:44 Ian Turton ha scritto:
> I agree with you. But until we do
I agree with you. But until we do a clean up we can't switch on an
automatic check.
Ian
On Sun, 10 Mar 2019, 12:38 Andrea Aime,
wrote:
> Hi Ian,
> that's a way to go but won't get me all the way to the objective... which
> is a build check.
> I'm not interested in doing a "one off" cleanup that
Hi Ian,
that's a way to go but won't get me all the way to the objective... which
is a build check.
I'm not interested in doing a "one off" cleanup that will have to be
repeated in a couple of
years, but setting a build check that will simply avoid this situation from
happening again
Cheers
Andrea
I'd vote for killing off anything that doesn't actually work and that has
been deprecated for a while to start and then looking at doing a clean up
"sprint" may be next bug stomp?
Ian
On Sat, 9 Mar 2019 at 19:22, Jody Garnett wrote:
> In a word - yay :)
>
> And yeah it is tough with things like
Hi,
among the deprecation issues a very bad one is the case
of FilterCapabilites and PostPreProcessFilterSplittingVisitor
deprecation. They have been deprecated, replacements provided, but none of
the code using them had been migrated.
This happened many years ago, and up to date, the situation is
