Mike,
it's more a tradition than a choice. version numbers symbolize more than simple
advancement. maintenance version counting is not named like that for nothing.
meaning if we really change/add something major (like menu positions), we have
to raise the version number to signalize it. i'd rat
Hi Ede,
I think there are also pros to move them now :
It will be easier for users to change habit if the plugin has not stayed
at the "wrong" place for years.
It seems obvious for RemoveSpike which has never been officially
released yet (I must put it right now where we collectively decided it
Mike,
can you keep that for after 1.9.1? moving menu entries should if possible not
happen between maintenance version releases.
..ede
On 11.03.2016 14:42, Giuseppe Aruta wrote:
> I also agree with your proposal Michael, about MakeValid and Remove Spike.
> Regarding Precision reducer, I prefer
I also agree with your proposal Michael, about MakeValid and Remove Spike.
Regarding Precision reducer, I prefer to have it on geometry.
Peppe
2016-03-11 14:32 GMT+01:00 Stefan Steiniger :
> my 2 cents: QA :) same for MakeValid
>
>
> On 3/11/16 04:53, Michaël Michaud wrote:
>
> Hi Peppe,
>
> Alwa
my 2 cents: QA :) same for MakeValid
On 3/11/16 04:53, Michaël Michaud wrote:
Hi Peppe,
Always difficult to "classify" plugins.
IMHO, RemoveSpike has not much to do with topology as it is not
intended to change feature topology (neither internal topology of
single features nor topology betwee
