<div dir="ltr"><div class="gmail_default" style="font-size:small">Thanks Tim and Giovanni!</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Sounds like a good approach. Let's try it.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Best wishes,</div><div class="gmail_default" style="font-size:small">Anita</div><div class="gmail_default" style="font-size:small"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Apr 30, 2017 at 11:11 PM, Tim Sutton <span dir="ltr"><<a href="mailto:tim@kartoza.com" target="_blank">tim@kartoza.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Hi PSC</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Following our meeting and our agreement that the 3.2 bug fixing funding should be diverted to 2.18 LTR bug fixing, I was chatting with Giovanni about triaging in prep for the paid bug fixing. In the past I think we didn't have a good workflow in terms of making a good prioritized list of issues to fix prior to launching the paid bug fixing. </div><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">​Andreas ​we would like to set up a process whereby before we do the call for developers to participate in paid bug fixing, we first make a list of priority issues (which Giovanni will help with) and then provide that list as part of the call for paid developers so that the developers who feel best qualified to resolve the issues can apply. Does that make sense for everyone?</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">For 2.18 LTR since we already have the call out for paid bug fixers, I would like to propose that we do this process retrospectively i.e. get Giovanni to make a prioritized list of issues needing attention for the LTR release and then ask the funded developers to focus their attention on that list in order of priority.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">One last thing we discussed will be to include a list of unresolved regressions / critical bugs in the changelog so that users can be clear when obtaining the release whether the remaining issues are critical in their work.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Any other thoughts / objections?</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Regards</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Tim</div><br></div><div><br></div>-- <br><div class="m_1911918854761851636gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div style="text-align:center">------------------------------<wbr>------------------------------<wbr>------------------------------</div><div style="text-align:center"><div style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif;font-size:small;display:inline">​</div><img src="cid:1A5DF6DE-E302-4C28-BFBD-29663CBF1351" style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px"><br></div><div style="text-align:center">Tim Sutton</div><div style="text-align:center"><span style="text-align:start">Visit </span><a href="http://kartoza.com/" style="text-align:start" target="_blank">http://kartoza.com</a><span style="text-align:start"> to find out about open source:</span><br style="text-align:start"><span style="text-align:start"> * Desktop GIS programming services</span><br style="text-align:start"><span style="text-align:start"> * Geospatial web development</span></div><div style="text-align:center"><span style="text-align:start">* GIS Training</span></div><div style="text-align:center"><span style="text-align:start">* Consulting Services</span></div><div style="text-align:center"><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:start"><div style="text-align:center">Tim is a member of the QGIS Project Steering Committee</div><div style="text-align:center">------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>-</div><div style="text-align:center">Kartoza is a merger between Linfiniti and Afrispatial</div></div></div></div></div></div></div>
</div>
<br>______________________________<wbr>_________________<br>
Qgis-psc mailing list<br>
<a href="mailto:Qgis-psc@lists.osgeo.org">Qgis-psc@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/qgis-psc</a><br></blockquote></div><br></div>