I'm a +1 on this proposal. I think having the core plugins in the repos is important so we can provide updates between QGIS versions.
- Nathan On Tue, Jul 24, 2012 at 9:27 PM, Paolo Cavallini <cavall...@faunalia.it> wrote: > Il 15/06/2012 19:01, Larry Shaffer ha scritto: >> Hmm, I assumed more flexible and timely updates was one of the points >> behind the idea to move parts of QGIS from C++ to Python, with its >> core, stable code base remaining in C++. Then more developers could >> help out with development and, like PyQGIS plugins, those modular >> Python components could be updated via a web-updater between releases, >> since Python code is byte-compiled on the user's machine. >> >> Was I incorrect in this assumption? >> >> It is now a common, maybe even expected, user experience to often >> web-update part or all of a program, beyond components such as >> contributed plugins. (I updated my git program, SourceTree, 3 times in >> the last week, because they needed to adapt to the new github.com API >> v.3.) > Hi all. > I think this topic is worth of attention: we will probably have to wait > a while to release e new version,because of API breakage and raster > changes, so in the meantime users should be able to have their plugins > fixed, even if they are core. > This couold be as simple as copying the plugins to the new repo, or > there is a better approach? > All the best. > > -- > 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@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
