[Qgis-developer] upgrading core plugins

[Tim Sutton]

Hi

On Tue, Jul 24, 2012 at 4:13 PM, Larry Shaffer <larrys at dakotacarto.com> wrote:
> On Tue, Jul 24, 2012 at 7:37 AM, Paolo Cavallini <cavallini at faunalia.it> wrote:
>> Il 24/07/2012 14:29, Jürgen E. Fischer ha scritto:
>>> Hi,
>>>
>>> On Tue, 24. Jul 2012 at 14:27:28 +0200, Jürgen E. Fischer wrote:
>>>> We probably should simply release more often - and get that process as lean as
>>>> possible, instead of putting work into making long release cycles less
>>>> painless.
>>> Um, if it's not clear anyway, I meant "less painful" :)
>> agreed, release often is A Good Thing.
>> unfortunately in the near future I guess it will not be possible, as the
>> major changes to raster imply we need quite a bit of testing and
>> polishing before releasing.
>> all the best.
>
> Concerning replication of the core plugins to repositories at
> plugins.qgis.org, maybe setting up each as a git submodule would help
> with this? While this will add complexity to the git setup, it allows
> for independent (but shared) repository commits and pushes to multiple
> remotes.
>
>
> From the user's point of view, getting updates to core plugins comes
> through Plugin Installer, which keys off of the plugin's version
> number. This leads to several circumstances that need addressed.
>
> * Core plugins replicated to plugins.qgis.org need to have a higher
> version number than the version that shipped with latest stable QGIS
> (obvious), to trigger the update.
> * Upon a new stable release, core plugins need their version bumped
> again, or the user's latest 'interim' core plugin update will mask the
> new stable version, since user-installed plugins of same version take
> precedence over core plugins.
> * When plugins become accepted to core their version number needs
> bumped for the same above masking reasons.
>
> Not sure what type of versioning core plugins should have, but for the
> last circumstance (accepted to core) the plugin's version needs to be
> higher than that previously used (so using QGIS's version number may
> not work for some, initially).
>
> My point here is that users should seamlessly receive update notices,
> regardless of how the update occurs. I think that requires standard
> plugin versioning, unless I'm missing another method.
>

Only downside to this is that I have never yet met someone who had
something good to say about using git submodules....

Regards

Tim

> Regards,
>
> Larry
>
>> --
>> Paolo Cavallini - Faunalia
>> www.faunalia.eu
>> Full contact details at www.faunalia.eu/pc
>> Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> 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
==============================================