Re: [QGIS-Developer] Trouble with ticket closure
> Hi all, > tickets are being automatically closed as end of life even if already > veruified against 3.0. I did a big job in testing many of them if not > all in Madeira HF and mark as 3.0 or (at that time) master. > Please revert the change, as this will make lots of valid tickets > disappear and will upset reporters. > No trouble at all, just 7/8 tickets were wrongly closed by mistake (among hundreds closed as agreed), and by chance they almost all belonged to you and I immediately reopened them. Next time just ask. -- G -- ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Trouble with ticket closure
Hi all, tickets are being automatically closed as end of life even if already veruified against 3.0. I did a big job in testing many of them if not all in Madeira HF and mark as 3.0 or (at that time) master. Please revert the change, as this will make lots of valid tickets disappear and will upset reporters. Thanks. -- Paolo Cavallini - www.faunalia.eu QGIS & PostGIS courses: http://www.faunalia.eu/training.html ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Plugin [1664] Add a point road sign approval notification.
Plugin Add a point road sign approval by pcav. The plugin version "[1664] Add a point road sign 0.2 Experimental" is now approved Link: http://plugins.qgis.org/plugins/Add_a_point_road_sign/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Improvement to the plugin manager's upgradeable plugins details
If it's not too much trouble for whomever manages the plugins site, it might be worth simply adding the changelog bit to plugins.xml and see the size difference then. I was initially worried but the more I think about it the more I get a feeling it should be just fine. On Sat, Mar 9, 2019, 7:14 PM Alessandro Pasotti wrote: > > > I like the idea, I'm just worried about the increased size of the XML on > option A: we don't have any control over the changelog size (well, we could > truncate the changelog if it's too long but I don't know if that makes much > sense). > > > > On Sat, Mar 9, 2019 at 11:38 AM Mathieu Pellerin > wrote: > >> Greetings, >> >> While applying a couple of commits to QGIS' plugin manager, I would like >> to fix a long-standing UX issue with it, namely that plugins that show a >> newer version available do _not_ show the latest changelog but rather the >> changelog of the currently installed plugin version. >> >> It'd much nicer, and exciting for users, to show what's new _prior to_ >> hitting the [ update plugin ] button. >> >> For that to happen, we'd need either: a/ add the changelog information in >> the repository XML file fetched (i.e. >> https://plugins.qgis.org/plugins/plugins.xml?qgis=3.6), or b/ add a >> method to fetch changelog strings from the repository site (for e.g., >> https://plugins.qgis.org/plugins/changelog.xml?names=plugin1,plugin2,plugin3 >> ). >> >> Unless adding the short changelog to the repository XML adds too many >> MBs, I'd vote for option A. >> >> Thoughts? >> >> Mathieu >> ___ >> QGIS-Developer mailing list >> QGIS-Developer@lists.osgeo.org >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > > > > -- > Alessandro Pasotti > w3: www.itopen.it > ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Improvement to the plugin manager's upgradeable plugins details
I like the idea, I'm just worried about the increased size of the XML on option A: we don't have any control over the changelog size (well, we could truncate the changelog if it's too long but I don't know if that makes much sense). On Sat, Mar 9, 2019 at 11:38 AM Mathieu Pellerin wrote: > Greetings, > > While applying a couple of commits to QGIS' plugin manager, I would like > to fix a long-standing UX issue with it, namely that plugins that show a > newer version available do _not_ show the latest changelog but rather the > changelog of the currently installed plugin version. > > It'd much nicer, and exciting for users, to show what's new _prior to_ > hitting the [ update plugin ] button. > > For that to happen, we'd need either: a/ add the changelog information in > the repository XML file fetched (i.e. > https://plugins.qgis.org/plugins/plugins.xml?qgis=3.6), or b/ add a > method to fetch changelog strings from the repository site (for e.g., > https://plugins.qgis.org/plugins/changelog.xml?names=plugin1,plugin2,plugin3 > ). > > Unless adding the short changelog to the repository XML adds too many MBs, > I'd vote for option A. > > Thoughts? > > Mathieu > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer -- Alessandro Pasotti w3: www.itopen.it ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Improvement to the plugin manager's upgradeable plugins details
> > On Sat, Mar 9, 2019 at 8:39 PM Mathieu Pellerin > wrote: > >> While applying a couple of commits to QGIS' plugin manager, I would like >> to fix a long-standing UX issue with it, namely that plugins that show a >> newer version available do _not_ show the latest changelog but rather the >> changelog of the currently installed plugin version. >> It'd much nicer, and exciting for users, to show what's new _prior to_ >> hitting the [ update plugin ] button. >> > +1 that would be really great! The current behavior doesn't make much sense. Anita ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Problem with running QGIS on Windows 10
Hi Jana, On Fri, 08. Mar 2019 at 19:53:47 +0100, Jana Michalková wrote: > Thanks in advance for any help! Try the procedure described in https://issues.qgis.org/issues/19061#note-16 to get more info about what's wrong. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Nordenhttps://www.norbit.de signature.asc Description: PGP signature norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH Rheinstrasse 13, 26506 Norden GF: Juergen Fischer, Nils Kutscher HR: Amtsgericht Aurich HRB 100827 Datenschutzerklaerung: https://www.norbit.de/83/ ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Improvement to the plugin manager's upgradeable plugins details
Ohh yes please. That is really needed! On Sat, Mar 9, 2019 at 8:39 PM Mathieu Pellerin wrote: > Greetings, > > While applying a couple of commits to QGIS' plugin manager, I would like > to fix a long-standing UX issue with it, namely that plugins that show a > newer version available do _not_ show the latest changelog but rather the > changelog of the currently installed plugin version. > > It'd much nicer, and exciting for users, to show what's new _prior to_ > hitting the [ update plugin ] button. > > For that to happen, we'd need either: a/ add the changelog information in > the repository XML file fetched (i.e. > https://plugins.qgis.org/plugins/plugins.xml?qgis=3.6), or b/ add a > method to fetch changelog strings from the repository site (for e.g., > https://plugins.qgis.org/plugins/changelog.xml?names=plugin1,plugin2,plugin3 > ). > > Unless adding the short changelog to the repository XML adds too many MBs, > I'd vote for option A. > > Thoughts? > > Mathieu > ___ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Improvement to the plugin manager's upgradeable plugins details
Greetings, While applying a couple of commits to QGIS' plugin manager, I would like to fix a long-standing UX issue with it, namely that plugins that show a newer version available do _not_ show the latest changelog but rather the changelog of the currently installed plugin version. It'd much nicer, and exciting for users, to show what's new _prior to_ hitting the [ update plugin ] button. For that to happen, we'd need either: a/ add the changelog information in the repository XML file fetched (i.e. https://plugins.qgis.org/plugins/plugins.xml?qgis=3.6), or b/ add a method to fetch changelog strings from the repository site (for e.g., https://plugins.qgis.org/plugins/changelog.xml?names=plugin1,plugin2,plugin3 ). Unless adding the short changelog to the repository XML adds too many MBs, I'd vote for option A. Thoughts? Mathieu ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
