Re: [Qgis-developer] 2.8.2?
Hello, Le mercredi 29 avril 2015, 08:11:57 Paolo Cavallini a écrit : Il 29/04/2015 08:07, kimaidou ha scritto: auto-update feature a la Firefox, but a simple warning could be a great addition IMHO. +1 Having a RSS feed on the website, with all released versions (stable/nightly/whatever) could be a generic tool. Then a short QGIS feature reading this feed and warning the user would be great. Vincent -- Vincent Picavet - Gérant Oslandia www.oslandia.com ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] 2.8.2?
Il 29/04/2015 08:07, kimaidou ha scritto: auto-update feature a la Firefox, but a simple warning could be a great addition IMHO. +1 -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] 2.8.2?
Hi all + 1 for Tim's proposal, as it is more readable and predictable. Another thing concerns me : I think many users are not in Twitter, or following the user or dev mailing list, and can easily miss the point release announcements. I think we could add in core a small tool which will behaves as the plugin manager, and warn the users whenever a new version of QGIS is available. I am not speaking of a complete (and complex) auto-update feature a la Firefox, but a simple warning could be a great addition IMHO. Regards Michaël 2015-04-28 21:13 GMT+02:00 Tim Sutton t...@kartoza.com: Hi Personally I think we should have a system that is simple to track (for users, developers and our beleaguered release manager) so that would rule out anything that requires individual assessment of patches. I very much like the idea of having a month end bugfix release even if there has been ‘too much activity’ for a calm period. Or even simpler yet have a fixed monthly release if there has been any activity in that month and don’t worry about the quiet period. The last week of the month could be a freeze period for testers and QA as per Juergen’s suggestion. This all sounds a bit like Microsoft’s ‘patch tuesday’ :-) If there is a critical fix for security or a real show stopper then we do an out of band release and otherwise just keep to the monthly cadence. Regards Tim On 28 Apr 2015, at 16:32, Sandro Santilli s...@keybit.net wrote: On Tue, Apr 28, 2015 at 01:23:35PM +0200, Jürgen E. Fischer wrote: Hi Sandro, On Tue, 28. Apr 2015 at 11:44:15 +0200, Sandro Santilli wrote: Let's try hard to avoid backports unless very very important ? PS: I'd be in favor of reducing the silence requirement to 1 week, especially for the first few bugfix releases... If only our largest gap was large enough to cover a week. commit 2e97ceb5c2ecc5c700cfeb42bf5bd822c7c9e91f Author: Werner Macho werner.ma...@gmail.com AuthorDate: Mon Mar 16 23:03:49 2015 +0100 Commit: Werner Macho werner.ma...@gmail.com CommitDate: Mon Mar 16 23:04:51 2015 +0100 adding french translators commit 6c7eb5b35c6d3c4331832be3811a186fa53d18ad Author: Nyall Dawson nyall.daw...@gmail.com AuthorDate: Tue Mar 10 22:53:23 2015 +1100 Commit: Nyall Dawson nyall.daw...@gmail.com CommitDate: Tue Mar 10 22:57:03 2015 +1100 Add some GDAL provider unit tests... Just ~6.5 days... Should adding french translators trigger a counter reset ? Doesn't sound like a commit that could possibly introduce regressions. Doesn't sound like an urgent fix either that can't wait for next patch level release to be included. Maybe by sending out periodical status report we can help all authors weight urgency of a release and importance of a fix. What notable changes since 2.8.2 ? So that wouldn't have helped either. Maybe we should do monthly point release with a week of no backports unless there were new bugs introduced. That would still give a week window to test the release nightlies before there is a release How's that different from asking developers to refrain from pushing changes but rather focus on tests for one week ? Such request would not be a general one, but contextual to a specific case in time. Like, now, as the point was raised a few times already, we could ask everyone to avoid pushing more changes in the stable branch unless really really important. Maybe asking on the list for more opinions about the convenience of pushing them. Until 2.8.2 is out. --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer — Tim Sutton Visit http://kartoza.com to find out about open source: * Desktop GIS programming services * Geospatial web development * GIS Training * Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net Tim is a member of the QGIS Project Steering Committee Kartoza is a merger between Linfiniti and Afrispatial ___ 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
Re: [Qgis-developer] 2.8.2?
On 28 Apr 2015, at 19:23, Jürgen E. Fischer j...@norbit.de wrote: Hi Sandro, On Tue, 28. Apr 2015 at 11:44:15 +0200, Sandro Santilli wrote: Let's try hard to avoid backports unless very very important ? PS: I'd be in favor of reducing the silence requirement to 1 week, especially for the first few bugfix releases... If only our largest gap was large enough to cover a week. snip Just ~6.5 days... So that wouldn't have helped either. Maybe we should do monthly point release with a week of no backports unless there were new bugs introduced. That would still give a week window to test the release nightlies before there is a release If you'll excuse a user sticking an oar in... I've been wondering if there oughtn't be a fall back release trigger. For example, there must be a point release to at the same time as the next normal release. Which would at least guarantee a point release happened. (Probably want something a bit more frequent than that. Or perhaps a bit offset from the normal, so there aren't two things being tested at once.) Anyway, first LTR experiment, RM's call on how it happens. -ramon. ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] 2.8.2?
Hi Sandro, On Tue, 28. Apr 2015 at 11:44:15 +0200, Sandro Santilli wrote: Let's try hard to avoid backports unless very very important ? PS: I'd be in favor of reducing the silence requirement to 1 week, especially for the first few bugfix releases... If only our largest gap was large enough to cover a week. commit 2e97ceb5c2ecc5c700cfeb42bf5bd822c7c9e91f Author: Werner Macho werner.ma...@gmail.com AuthorDate: Mon Mar 16 23:03:49 2015 +0100 Commit: Werner Macho werner.ma...@gmail.com CommitDate: Mon Mar 16 23:04:51 2015 +0100 adding french translators commit 6c7eb5b35c6d3c4331832be3811a186fa53d18ad Author: Nyall Dawson nyall.daw...@gmail.com AuthorDate: Tue Mar 10 22:53:23 2015 +1100 Commit: Nyall Dawson nyall.daw...@gmail.com CommitDate: Tue Mar 10 22:57:03 2015 +1100 Add some GDAL provider unit tests... Just ~6.5 days... So that wouldn't have helped either. Maybe we should do monthly point release with a week of no backports unless there were new bugs introduced. That would still give a week window to test the release nightlies before there is a release 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 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: Digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] 2.8.2?
Il 28/04/2015 11:44, Sandro Santilli ha scritto: Let's try hard to avoid backports unless very very important ? -1 backports are useful, otherwise thaty would not have been done. perhaps a moving window as suggested by Juergen could be a solution. thanks. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] 2.8.2?
Hi Personally I think we should have a system that is simple to track (for users, developers and our beleaguered release manager) so that would rule out anything that requires individual assessment of patches. I very much like the idea of having a month end bugfix release even if there has been ‘too much activity’ for a calm period. Or even simpler yet have a fixed monthly release if there has been any activity in that month and don’t worry about the quiet period. The last week of the month could be a freeze period for testers and QA as per Juergen’s suggestion. This all sounds a bit like Microsoft’s ‘patch tuesday’ :-) If there is a critical fix for security or a real show stopper then we do an out of band release and otherwise just keep to the monthly cadence. Regards Tim On 28 Apr 2015, at 16:32, Sandro Santilli s...@keybit.net wrote: On Tue, Apr 28, 2015 at 01:23:35PM +0200, Jürgen E. Fischer wrote: Hi Sandro, On Tue, 28. Apr 2015 at 11:44:15 +0200, Sandro Santilli wrote: Let's try hard to avoid backports unless very very important ? PS: I'd be in favor of reducing the silence requirement to 1 week, especially for the first few bugfix releases... If only our largest gap was large enough to cover a week. commit 2e97ceb5c2ecc5c700cfeb42bf5bd822c7c9e91f Author: Werner Macho werner.ma...@gmail.com AuthorDate: Mon Mar 16 23:03:49 2015 +0100 Commit: Werner Macho werner.ma...@gmail.com CommitDate: Mon Mar 16 23:04:51 2015 +0100 adding french translators commit 6c7eb5b35c6d3c4331832be3811a186fa53d18ad Author: Nyall Dawson nyall.daw...@gmail.com AuthorDate: Tue Mar 10 22:53:23 2015 +1100 Commit: Nyall Dawson nyall.daw...@gmail.com CommitDate: Tue Mar 10 22:57:03 2015 +1100 Add some GDAL provider unit tests... Just ~6.5 days... Should adding french translators trigger a counter reset ? Doesn't sound like a commit that could possibly introduce regressions. Doesn't sound like an urgent fix either that can't wait for next patch level release to be included. Maybe by sending out periodical status report we can help all authors weight urgency of a release and importance of a fix. What notable changes since 2.8.2 ? So that wouldn't have helped either. Maybe we should do monthly point release with a week of no backports unless there were new bugs introduced. That would still give a week window to test the release nightlies before there is a release How's that different from asking developers to refrain from pushing changes but rather focus on tests for one week ? Such request would not be a general one, but contextual to a specific case in time. Like, now, as the point was raised a few times already, we could ask everyone to avoid pushing more changes in the stable branch unless really really important. Maybe asking on the list for more opinions about the convenience of pushing them. Until 2.8.2 is out. --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer — Tim Sutton Visit http://kartoza.com http://kartoza.com/ to find out about open source: * Desktop GIS programming services * Geospatial web development * GIS Training * Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net Tim is a member of the QGIS Project Steering Committee Kartoza is a merger between Linfiniti and Afrispatial ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] 2.8.2?
On Mon, Apr 27, 2015 at 10:52:18PM +, Nathan Woodrow wrote: Sorry to be a pain in the butt but do we have a update on when we could expect a 2.8.2 release? It's up to us all. If we handle to stop pushing changes to the 2.8 branch for two weeks, we get the 2.8.2 release cut. I see a lot of emails of late all hitting the bugs that have been fixed for this release. Let's try hard to avoid backports unless very very important ? PS: I'd be in favor of reducing the silence requirement to 1 week, especially for the first few bugfix releases... --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] 2.8.2?
On 23 March 2015 at 19:14, Sandro Santilli s...@keybit.net wrote: On Sun, Mar 22, 2015 at 10:49:24PM +0100, Anita Graser wrote: Hi, On Wed, Mar 11, 2015 at 4:01 PM, Paolo Cavallini cavall...@faunalia.it wrote: Il 11/03/2015 15:15, Jürgen E. Fischer ha scritto: There already is a nightly build of the release branch in OSGeo4W now (package qgis-rel-dev since march 5th). Thanks Juergen. I think a standalone installer would be important now, I know that fixes/backports haven't really slowed down yet ( https://github.com/qgis/QGIS/commits/release-2_8) but is there a date for 2.8.2? For example, the already fixed heatmap plugin issue keeps popping up every other day ... I would note that there are currently 11 tickets having 2.8.2 as their target, 6 of which are marked as Blocker. I dunno how to provide an URL to quickly point to that list of 6-11. I don't think blocker has much meaning in this context. They aren't new issues which don't exist in 2.8.1, and if no-one is actively working on fixing them then they can wait to = 2.8.3. In the meantime we've got a stackload of nice bug fixes waiting in 2.8 branch for a release... Nyall ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] 2.8.2?
On Mon, Mar 23, 2015 at 07:30:26PM +1100, Nyall Dawson wrote: On 23 March 2015 at 19:14, Sandro Santilli s...@keybit.net wrote: On Sun, Mar 22, 2015 at 10:49:24PM +0100, Anita Graser wrote: I know that fixes/backports haven't really slowed down yet ( https://github.com/qgis/QGIS/commits/release-2_8) but is there a date for 2.8.2? For example, the already fixed heatmap plugin issue keeps popping up every other day ... I would note that there are currently 11 tickets having 2.8.2 as their target, 6 of which are marked as Blocker. I dunno how to provide an URL to quickly point to that list of 6-11. I don't think blocker has much meaning in this context. They aren't new issues which don't exist in 2.8.1, and if no-one is actively working on fixing them then they can wait to = 2.8.3. In the meantime we've got a stackload of nice bug fixes waiting in 2.8 branch for a release... I suggest creating a new 2.8.3 target in hub then, and start moving issues there (those that are not regressions introduced by 2.8.1, if any). Then, by *requiring* that any commit in 2.8 *must* reference a ticket in hub, release management can happen from there (hub), allowing for a per-ticket discussion (if needed). It would help to have a way to make hub queries accessible via a simple link. Does any such thing exist in redmine ? Similar to reports for trac... --strk; () Free GIS Flash consultant/developer /\ http://strk.keybit.net/services.html ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] 2.8.2?
On Sun, Mar 22, 2015 at 10:49:24PM +0100, Anita Graser wrote: Hi, On Wed, Mar 11, 2015 at 4:01 PM, Paolo Cavallini cavall...@faunalia.it wrote: Il 11/03/2015 15:15, Jürgen E. Fischer ha scritto: There already is a nightly build of the release branch in OSGeo4W now (package qgis-rel-dev since march 5th). Thanks Juergen. I think a standalone installer would be important now, I know that fixes/backports haven't really slowed down yet ( https://github.com/qgis/QGIS/commits/release-2_8) but is there a date for 2.8.2? For example, the already fixed heatmap plugin issue keeps popping up every other day ... I would note that there are currently 11 tickets having 2.8.2 as their target, 6 of which are marked as Blocker. I dunno how to provide an URL to quickly point to that list of 6-11. --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] 2.8.2?
On Mon, Mar 23, 2015 at 06:28:55PM +0100, Matthias Kuhn wrote: It may just be me, but I don't think any of this brings a huge benefit. The rule also brings some overhead. When I find a bug that's not in the tracker I prefer to just fix it and describe what has been done in the commit message. Creating an issue for that is a bit cumbersome. It is, but that's part of augmenting stability value of the branch. If it's not worth the trouble of burocracy, then it's not so important to be fixed .. For bitcoins it works :) https://en.bitcoin.it/wiki/Proof_of_work --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] 2.8.2?
Hi, On Wed, Mar 11, 2015 at 4:01 PM, Paolo Cavallini cavall...@faunalia.it wrote: Il 11/03/2015 15:15, Jürgen E. Fischer ha scritto: There already is a nightly build of the release branch in OSGeo4W now (package qgis-rel-dev since march 5th). Thanks Juergen. I think a standalone installer would be important now, I know that fixes/backports haven't really slowed down yet ( https://github.com/qgis/QGIS/commits/release-2_8) but is there a date for 2.8.2? For example, the already fixed heatmap plugin issue keeps popping up every other day ... Best wishes, Anita however. All the best. -- Paolo Cavallini - www.faunalia.eu QGIS PostGIS courses: http://www.faunalia.eu/training.html ___ 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
Re: [Qgis-developer] 2.8.2?
Hi Paolo, On Tue, 10. Mar 2015 at 11:31:06 +0100, Paolo Cavallini wrote: We have 20 fixes backported, some of them rather important: would it be time to release a 2.8.2? There already is a nightly build of the release branch in OSGeo4W now (package qgis-rel-dev since march 5th). 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 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode signature.asc Description: Digital signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] 2.8.2?
On Tue, Mar 10, 2015 at 11:53:28AM +0100, Paolo Cavallini wrote: Hi all. Il 10/03/2015 11:46, Sandro Santilli ha scritto: Communicated policy was that any new patch-level release is cut (automatically, I've understood) after 2 weeks of silence in the stable branch: REF: http://lists.osgeo.org/pipermail/qgis-developer/2015-March/037043.html Latest change was today: https://github.com/qgis/qgis/commits/release-2_8 IMHO it is quite likely that in the first weeks there will be continuous activity fixing the newly discovered bugs. The 2 weeks delay is fine on the long term, but in the first period I would suggest a release based on important fixes. Is there an updated human-readable list of bugs fixed in the branch ? It would be helpful to have such list always updated for each commit so we can look at it quickly and judge the if any item warrants an urgent release. A GET-encoded query to the bug tracker could also do, if that's supported by HUB. PS: commits are still coming in the stable branch, latest one 5 hours ago. --strk; ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer
