Hi On Sun, Apr 15, 2012 at 10:55 PM, Borys Jurgiel <[email protected]> wrote: >> This confirms what I've seen in the past: if a core plugin is released via >> a user repository channel, and the user installs it, the installed user >> plugin takes precedence over the core module of the same package name (e.g. >> fTools user plugin is used instead of fTools core plugin). >> >> So, it is my understanding that a core plugin shipping with a release would >> not be 'pinned down' to the QGIS release schedule. > > Yes, exactly. You can release a plugin update this way and it mask the one > bundled with Qgis release. If, some day, the user upgrades qgis and the > version of the plugin bundled with master becomes higher that the one > available in the repository, QGIS displays a message to encouage user to > uninstall the update, that is now outdated. >
Well +1 from me to include the atlas plugin +1 from me to include the db manager plugin Regards Tim _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) ============================================== Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net ============================================== _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
