<div dir="ltr">I agree too. "Processing" is massive and to fully test it is going to take while. <div><br></div><div>Also, considering the interest of the community and the number of new features that are added or requested in the bug tracker/GIS Stackexchange every day, I think scheduling frequent releases is the best way to keep Processing evolving and maturing. </div>
<div><br></div><div>As always, I would like to thank Victor Olaya for bringing Sextante/Processing to QGIS. It has greatly improved my GIS work and made it a lot more enjoyable. I think sometime ago Camilo Polymeris said something like "the more into Sextante, the more I like it". I feel the same way about using it.<br>
</div><div><br>Regards</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Oct 6, 2013 at 8:30 PM, Pedro Venāncio <span dir="ltr"><<a href="mailto:pedrongvenancio@yahoo.com" target="_blank">pedrongvenancio@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I also think the best option is to provide updates of Processing in the plugin repo. Processing is still evolving and much bugfixing has been done and is done regularly. In my opinion, these fixes must be backported more regularly than the QGIS releases.<br>
<br>
<br>
Best regards,<br>
Pedro<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
<br>
----- Original Message -----<br>
<br>
I have discussed with Tim the idea of releasing new versions of<br>
Processing periodically, tagged as experimental, to the plugin repo.<br>
Alex has prepared a script that packages and uploads the Processing<br>
code, and that can be used to automate that, but we haven't done<br>
anything yet regarding that. What do people think of this idea?<br>
<br>
If a new QGIS release is made, the master version cntains quite a few<br>
bug fixes for Processing.<br>
<br>
Cheers<br>
Victor<br>
<br>
2013/10/6 Paolo Cavallini <<a href="mailto:cavallini@faunalia.it">cavallini@faunalia.it</a>>:<br>
> -----BEGIN PGP SIGNED MESSAGE-----<br>
> Hash: SHA1<br>
><br>
> Il 06/10/2013 21:07, Victor Olaya ha scritto:<br>
>> That is already fixed in master<br>
><br>
> Hi all.<br>
> What are the plans for this?Are we going to backport and release a<br>
> fixed version?<br>
> This question concerns a few other fixed bugs, I believe.<br>
> All the best.<br>
><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.14 (GNU/Linux)<br>
> Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a><br>
><br>
> iEYEARECAAYFAlJRtcgACgkQ/NedwLUzIr6lHQCfZI8bj/ZW0bqNKvDDoZo32N7E<br>
> JcwAn0mvz/QeZl3zEWs0Ke6GbwSQZcnf<br>
> =I60/<br>
> -----END PGP SIGNATURE-----<br>
> _______________________________________________<br>
> Qgis-developer mailing list<br>
> <a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
<br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</div></div></blockquote></div><br></div>