← Back to team overview

hugin-devs team mailing list archive

[Bug 1002474] [NEW] api-max setting for python plugins is only activated for stable releases

 

Public bug reported:

The python plugins have an 'api-max' value to prevent older plugins
being run with future releases of Hugin.

However this restriction is only enforced for stable even-numbered
releases, i.e. The plugins shipped with 2011.4.0 are disabled, but they
are not disabled with 2011.3.0 and 2011.5.0 snapshots. See
src/hugin1/hugin/PluginItems.cpp line 142.

The problem is that since most people who are in a position to check
this compatibility are using snapshots, they will never notice that the
api-max value needs incrementing.

So either:

The api-max check needs to be removed altogether.

..or it should be automatically set to the current release number, since
we should only be shipping compatible plugins.

..or it should be enforced for snapshots too - Making it more likely
that it will get fixed when a developer notices that plugins are
missing.

** Affects: hugin
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1002474

Title:
  api-max setting for python plugins is only activated for stable
  releases

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  The python plugins have an 'api-max' value to prevent older plugins
  being run with future releases of Hugin.

  However this restriction is only enforced for stable even-numbered
  releases, i.e. The plugins shipped with 2011.4.0 are disabled, but
  they are not disabled with 2011.3.0 and 2011.5.0 snapshots. See
  src/hugin1/hugin/PluginItems.cpp line 142.

  The problem is that since most people who are in a position to check
  this compatibility are using snapshots, they will never notice that
  the api-max value needs incrementing.

  So either:

  The api-max check needs to be removed altogether.

  ..or it should be automatically set to the current release number,
  since we should only be shipping compatible plugins.

  ..or it should be enforced for snapshots too - Making it more likely
  that it will get fixed when a developer notices that plugins are
  missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1002474/+subscriptions


Follow ups

References