[Qgis-user] Where to get a current build without using OSGeo4W

[Jonathan Moules]

HI Werner,
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.

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
sourcepole.ch. This must result in a lot of duplication.
I was also surprised at the huge number of commercial support providers
QGIS has compared to GeoServer which does ~monthly point releases.
Thanks again,
Jonathan

On 26 April 2013 11:00, Werner Macho <werner.macho at gmail.com> wrote:

> Hi Jonathan!
> We already tried to do that with the 1.7.x release ..
> But there were several points:
>
> 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)
> 2. we lack developers doing that (compared with other projects QGIS has
> few developers)
> 3. there are more important things (fix bugs in current version instead of
> backporting bugfixes to an rather old version)
>
> But if I remember correct sourcepole.ch 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..
> but don't rely on that inforation from me - take a look by yourself ..
>
> kind regards
> Werner
>
>
> On Fri, Apr 26, 2013 at 11:41 AM, Jonathan Moules <
> jonathanmoules at warwickshire.gov.uk> wrote:
>
>>  On 26 April 2013 07:04, Paolo Cavallini <cavallini at faunalia.it> wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Il 25/04/2013 16:38, Jonathan Moules ha scritto:
>>> > Thanks Both. It's blocked by web-sense; it doesn't like the Curl
>>> component ("proxy
>>> > avoidance" - pah). I tried downloading it separately at home and
>>> bringing it in but
>>> > to no avail.
>>>
>>> I do not see why this shouldn't work.
>>>
>> Me neither, but it didn't.
>>
>>
>>>
>>> > I must admit, it would be nice if QGIS released more intermediate
>>> stable builds (i.e.
>>> > patches), rather than force folks to get nightly builds for bug fixes.
>>>
>>> Intermediate builds are not stable by definition. In principle there is
>>> no problem in
>>> releasing (e.g. monthly) standalones for qgis-dev, but it must be made
>>> clear that
>>> they are previews, not production ready.
>>>
>>
>> To clarify - I mean more builds that actually have patches and stuff. Not
>> a sub-set of "new" features from the next version.
>>  So for instance, currently QGIS does this:
>> 1.8.0 - June 2012
>> 2.x - future (201?)
>>
>> 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.
>> 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.).
>>
>> Hope that clarifies.
>> Jonathan
>>
>>
>>
>>
>>
>>> If you want to do it, or are ready to sponsor the effort, you're welcome.
>>> All the best.
>>> - --
>>> Paolo Cavallini - Faunalia
>>> www.faunalia.eu
>>> Full contact details at www.faunalia.eu/pc
>>> Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.12 (GNU/Linux)
>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>
>>> iEYEARECAAYFAlF6GNIACgkQ/NedwLUzIr7yqQCdGJI7FPChfP7D13TdlsCbpV8J
>>> +e4AoKTIDB9ld7sZW1UCenv5HPDA5RHL
>>> =AlLr
>>> -----END PGP SIGNATURE-----
>>> _____ __________________
_______ _________________
>>> Qgis-user mailing list
>>> Qgis-user at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/qgis-user
>>>
>>
>>
>>
>> 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.
>>
>> ________________________
_______________________
>> Qgis-user mailing list
>> Qgis-user at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-user
>>
>>
>


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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20130426/b5dab58b/attachment.html>