[Qgis-developer] Version number in plugin path - So where the matter was dropped?

[Borys Jurgiel]

Tuesday 11 of November 2008 16:31:34 Martin Dobias napisał(a):
> Borys,
>
> On Tue, Nov 11, 2008 at 4:14 PM, Borys Jurgiel <borys at wolf.most.org.pl> 
wrote:
> > What form do we fix? I suggest the following:
> >
> > def qgisMinimumVersion():
> >  return '1.0.0'
> >
> > Where returned string contains two or three (both cases are allowed)
> > integer values separated by points.
> >
> > The important question is if we expect one of the values to be more than
> > 9. If not, we can just compare them as strings. But '10' < '9', so if
> > version 1.0.10 or 1.10.0 is expected, we need to extract each level and
> > compare separately as integer. In this case we should be prepared that
> > the plugin author may put some suffix to this string, what might raise
> > exception. In the former case such suffix will be confusing too, because
> > '1.0preview2' > '1.0'.
>
> you have to expect also partial version values > 9.
> QGIS releases must be versioned correctly, i.e. always use scheme
> "x.y.z-txt". Project file versioning already depends on this fact, so the
> same should be expected in plugin installer.

Ok. This way I've made an universal python module for version comparing. 
I'm only hesitating where to insert 'preview' to the existing order:
'alpha' < 'beta' < 'rc' < [no_suffix] = 'final' < [any other suffix]

I think after the alpha, beta and rc rather then before. I'll add it to 
Installer as a separate module soon, so everyone will can take it for his own 
purposes.

> > And for repository metadata I suggest the following form:
> >
> > <qgisMinimumVersion>
> > 1.0.0
> > </qgisMinimumVersion>
>
> Agreed.

Sorry, rather <qgis_minimum_version> to meet existing naming style.

Regards,
B.