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