<div dir="ltr"><div><div><div><div>Hi all<br><br></div>+ 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<br></div> "a la Firefox", but a simple warning could be a great addition IMHO.<br><br></div>Regards<br></div>Michaël<br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-04-28 21:13 GMT+02:00 Tim Sutton <span dir="ltr"><<a href="mailto:tim@kartoza.com" target="_blank">tim@kartoza.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi<div><br></div><div><br></div><div>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.</div><div><br></div><div>Regards</div><div><br></div><div>Tim</div><div><br></div><div><br></div><div><div><div class="h5"><br><blockquote type="cite">On 28 Apr 2015, at 16:32, Sandro Santilli <<a href="mailto:strk@keybit.net" target="_blank">strk@keybit.net</a>> wrote:<br><br>On Tue, Apr 28, 2015 at 01:23:35PM +0200, Jürgen E. Fischer wrote:<br><blockquote type="cite" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Hi Sandro,<br><br>On Tue, 28. Apr 2015 at 11:44:15 +0200, Sandro Santilli wrote:<br><blockquote type="cite">Let's try hard to avoid backports unless very very important ?<br><br>PS: I'd be in favor of reducing the silence requirement to 1 week,<br> especially for the first few bugfix releases...<br></blockquote><br>If only our largest gap was large enough to cover a week.<br><br>commit 2e97ceb5c2ecc5c700cfeb42bf5bd822c7c9e91f<br>Author: Werner Macho <<a href="mailto:werner.macho@gmail.com" target="_blank">werner.macho@gmail.com</a>><br>AuthorDate: Mon Mar 16 23:03:49 2015 +0100<br>Commit: Werner Macho <<a href="mailto:werner.macho@gmail.com" target="_blank">werner.macho@gmail.com</a>><br>CommitDate: Mon Mar 16 23:04:51 2015 +0100<br><br> adding french translators<br><br>commit 6c7eb5b35c6d3c4331832be3811a186fa53d18ad<br>Author: Nyall Dawson <<a href="mailto:nyall.dawson@gmail.com" target="_blank">nyall.dawson@gmail.com</a>><br>AuthorDate: Tue Mar 10 22:53:23 2015 +1100<br>Commit: Nyall Dawson <<a href="mailto:nyall.dawson@gmail.com" target="_blank">nyall.dawson@gmail.com</a>><br>CommitDate: Tue Mar 10 22:57:03 2015 +1100<br><br>Add some GDAL provider unit tests...<br><br>Just ~6.5 days...<br></blockquote><br>Should "adding french translators" trigger a "counter reset" ?<br>Doesn't sound like a commit that could possibly introduce regressions.<br>Doesn't sound like an urgent fix either that can't wait for next<br>patch level release to be included. Maybe by sending out periodical<br>status report we can help all authors weight urgency of a release and<br>importance of a fix. What notable changes since 2.8.2 ?<br><br><blockquote type="cite" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">So that wouldn't have helped either. Maybe we should do monthly point release<br>with a week of no backports unless there were new bugs introduced. That would<br>still give a week window to test the release nightlies before there is a<br>release<br></blockquote><br>How's that different from asking developers to refrain from pushing changes<br>but rather focus on tests for one week ? Such request would not be a general<br>one, but contextual to a specific case in time. Like, now, as the point was<br>raised a few times already, we could ask everyone to avoid pushing more<br>changes in the stable branch unless really really important. Maybe asking on<br>the list for more opinions about the convenience of pushing them. Until<br>2.8.2 is out.<br><br>--strk;<br>_______________________________________________<br>Qgis-developer mailing list<br><a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br></blockquote><br></div></div><div><span>—</span><br><span><br></span><span style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br><span><img src="cid:62C890D4-3964-4609-BDE6-7536D5FBDD70" height="66" width="160"></span><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-align:center"><br><br></div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-align:center">Tim Sutton</div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-align:center"><br></div><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="text-align:center">Visit <a href="http://kartoza.com" target="_blank">http://kartoza.com</a> to find out about open source:</div><div style="text-align:center"><br></div><div><div style="text-align:center">* Desktop GIS programming services</div><div style="text-align:center">* Geospatial web development</div><div style="text-align:center">* GIS Training</div><div style="text-align:center">* Consulting Services</div><div style="text-align:center"><br></div><div><div style="text-align:center">Skype: timlinux Irc: timlinux on #qgis at <a href="http://freenode.net" target="_blank">freenode.net</a></div><div style="text-align:center">Tim is a member of the QGIS Project Steering Committee</div><div style="text-align:center"><br></div><div style="text-align:center">Kartoza is a merger between Linfiniti and Afrispatial</div></div></div></div>
</span></div><br></div></div><br>_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br></blockquote></div><br></div>