HI Werner,<div>Thanks for the information. I guess if/when I convince WCC to look into QGIS as a corporate solution we'll investigate commercial support at that time, and this will be one of the issues that I'll keep an eye out for.</div>
<div><br></div><div>But it does occur to me - there's no point getting a bug fixed in a timely fashion (commercial support) if you need to wait n months until the next official release to get the fixed version. So surely updated builds must be being created for the commercially supported, i.e. like your mentioned <a href="http://sourcepole.ch" target="_blank">sourcepole.ch</a>. This must result in a lot of duplication.</div>
<div>I was also surprised at the huge number of commercial support providers QGIS has compared to GeoServer which does ~monthly point releases.<br><div>Thanks again,</div><div>Jonathan</div><br><div class="gmail_quote">On 26 April 2013 11:00, Werner Macho <span dir="ltr"><<a href="mailto:werner.macho@gmail.com" target="_blank">werner.macho@gmail.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">Hi Jonathan!<div>We already tried to do that with the 1.7.x release ..</div><div>But there were several points:</div><div><br></div><div>1. it turned out that development is currently such fast that it takes more than just doing "apply patch from master back to 1.7.x (or 1.8.x)</div>
<div>2. we lack developers doing that (compared with other projects QGIS has few developers)</div><div>3. there are more important things (fix bugs in current version instead of backporting bugfixes to an rather old version)</div>
<div><br></div><div>But if I remember correct <a href="http://sourcepole.ch" target="_blank">sourcepole.ch</a> is backporting and trying to fix bugs in a stable release (currently 1.8?) and give that to companies with a support contract with them .. probably that would also be something for you..</div>
<div>but don't rely on that inforation from me - take a look by yourself ..</div><div><br></div><div>kind regards</div><span><font color="#888888"><div>Werner</div></font></span></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Fri, Apr 26, 2013 at 11:41 AM, Jonathan Moules <span dir="ltr"><<a href="mailto:jonathanmoules@warwickshire.gov.uk" target="_blank">jonathanmoules@warwickshire.gov.uk</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style
="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><div>On 26 April 2013 07:04, Paolo Cavallini <span dir="ltr"><<a href="mailto:cavallini@faunalia.it" target="_blank">cavallini@faunalia.it</a>></span> wrote:</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA1<br><br>Il 25/04/2013 16:38, Jonathan Moules ha scritto:<br><div>> Thanks Both. It's blocked by web-sense; it doesn't like the Curl component ("proxy<br>> avoidance" - pah). I tried downloading it separately at home and bringing it in but<br>
> to no avail.<br><br></div>I do not see why this shouldn't work.<br></blockquote><div>Me neither, but it didn't.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>> I must admit, it would be nice if QGIS released more intermediate stable builds (i.e.<br>> patches), rather than force folks to get nightly builds for bug fixes.<br><br></div>Intermediate builds are not stable by definition. In principle there is no problem in<br>
releasing (e.g. monthly) standalones for qgis-dev, but it must be made clear that<br>they are previews, not production ready.<br></blockquote><div><br></div><div>To clarify - I mean more builds that actually have patches and stuff. Not a sub-set of "new" features from the next version.</div>
<div>So for instance, currently QGIS does this:</div><div>1.8.0 - June 2012</div><div>2.x - future (201?)</div><div><br></div><div>And that's it. If I want fixes for any of the numerous bugs in 1.8.0, many of which have been fixed, I have to use an unstable, unsupported build (i.e., NextGIS). For personal use I have no issue using such a build, but I can't really justify it at a corporate level.</div>
<div>What many other projects do is they provide intermittent point releases which fix the more egregious bugs. New features still only come in the major releases (1.7, 1.8, 2.0 etc.).</div><div><br></div><div>Hope that clarifies.</div>
<div>Jonathan</div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If you want to do it, or are ready to sponsor the effort, you're welcome.<br>
All the best.<br>- --<br>Paolo Cavallini - Faunalia<br><a href="http://www.faunalia.eu" target="_blank">www.faunalia.eu</a><br>Full contact details at <a href="http://www.faunalia.eu/pc" target="_blank">www.faunalia.eu/pc</a><br>
Nuovi corsi QGIS e PostGIS: <a href="http://www.faunalia.it/calendario" target="_blank">http://www.faunalia.it/calendario</a><br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.12 (GNU/Linux)<br>Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a><br>
<br>iEYEARECAAYFAlF6GNIACgkQ/NedwLUzIr7yqQCdGJI7FPChfP7D13TdlsCbpV8J<br>+e4AoKTIDB9ld7sZW1UCenv5HPDA5RHL<br>=AlLr<br>-----END PGP SIGNATURE-----<br><div><div>_____
_________________________
_________________<br>Qgis-user mailing list<br><a href="mailto:Qgis-user@lists.osgeo.org" target="_blank">Qgis-user@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>
</div></div></blockquote></div><br><br><br></div></div><div>This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.<br>
<br></div><div>____________________
_________________________
__<br>Qgis-user mailing list<br><a href="mailto:Qgis-user@lists.osgeo.org" target="_blank">Qgis-user@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><br><br></div></blockquote></div><br></div></blockquote></div><br></div><BR>
<BR>
This transmission is intended for the named addressee(s) only and may contain sensitive or protectively marked material up to RESTRICTED and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please notify the sender immediately. All email traffic sent to or from us, including without limitation all GCSX traffic, may be subject to recording and/or monitoring in accordance with relevant legislation.<BR>