[Qgis-developer] Failing tests consider blockers
radim.blazek at gmail.com
Wed Feb 19 00:14:43 PST 2014
On Sun, Feb 16, 2014 at 11:41 PM, Jürgen E. <jef at norbit.de> wrote:
> What I wanted to say is that there are a bunch of tests that fail because they
> are not up to date or fail for other reasons that are not related to actual
> bugs in qgis itself. For example render tests, which fail because of fonts or
> other differences (eg. removed renderers). I think that are the majority of
> tests that currently fail.
Platform dependent tests (fonts) don't make sense for me and should be
disabled until get fixed (e.g. using font set shipped with QGIS).
Renderer test should be updated and only real bugs will remain and
those should be blockers, I think.
> So the tests need work. But that's a known fact and it's not at all new. Still
> not much has been done about it - except talk.
I have fixed WCS, I'll disable those platform dependent and look at
renderer test. I don't know much (never worked on) about others like
PyQgsDelimitedTextProvider, geometrytest, openstreetmaptest,
> Another thing is that we don't have the concept of actual blockers anymore. We
> release every four months what we have at that point. Blockers are just
> highest priority for bugs.
Blockers do not block stable release?! I don't think anything like
that was ever explicitly said nor there is a general consensus about
that. I read your release plan again and I only found:
On Tue, Nov 5, 2013 at 11:23 AM, Jürgen E. <jef at norbit.de> wrote:
> So the release should just be determined just by time and be not be tied to
> some desireable feature set/level of improvement or some other thing that might
> or might not have happened at a given point in time and delay the next release
> for an unknown amount of time.
which I did not read as "may be released with blockers". Do you say
that 2.2 may be released with issues marked as blockers?
More information about the Qgis-developer