<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Papyrus;
panose-1:3 7 5 2 6 5 2 3 2 5;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Thanks Anita for the survey. I think it really important that there is some feedback on the LTR issue. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As I have posted before, the difficulty with constant change in software lies with the use of software in institutions where everyone has to be using the same release in order for everything to be compatible. By everything I mean training, templates and styles and workflows so that the team is all working together. I also note that training material needs to catch up with rapid changes in the LTR. There is nothing more frustrating than finding a workflow that solves your problem only to discover that the Video is for 2.8 and the workflow changed in 3.4 and you are using 3.10. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>These are the reasons for supporting a longer Ltr life.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I think it also important that the QGIS page clearly explains the difference between the different releases and the Ltr and the implications for deployment in workplace or for a project team.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I should note that I think the continuing development of QGIS is wonderful and very responsive to user interests but as QGIS become more embedded in business and project teams there are practical implications for rapid change of the basic software.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Regards<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b><span style='font-size:12.0pt;font-family:Papyrus;mso-fareast-language:EN-AU'>Dr Iain Stuart<o:p></o:p></span></b></p><p class=MsoNormal><b><i><span style='font-size:12.0pt;font-family:Papyrus;mso-fareast-language:EN-AU'>JCIS Consultants <o:p></o:p></span></i></b></p><p class=MsoNormal><span style='mso-fareast-language:EN-AU'>P.O. Box 2397<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-AU'>Burwood North<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-AU'>NSW, 2134<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-AU'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-AU'>(02) 9701 0191<br>(0413) 380116 (m)<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>