Il 16/09/2012 22:13, Tim Sutton ha scritto:
Yes if you refer back to hte original discussion of moving SEXTANTE to
QGIS core, you will see that I mentioned we can set up an automated
export of the SEXTANTE plugin. We just need to determine the rules
about how and when such exports should be
Il 16/09/2012 06:56, Nathan Woodrow ha scritto:
Why don't we have the core python plugins are git sub modules we can
then host the code in a separate repo on github but pull it into the
main code base using git submodules [0]
This way they can be included in the main core release but can
Hi
On Sat, Sep 15, 2012 at 10:10 AM, Filipe Dias filipesd...@gmail.com wrote:
Hi,
Some of us (regular Sextante testers) were using Tortoise svn (Windows) to
download the latest code revision of Sextante. As soon as Victor Olaya
solved one of the bugs we reported, we would download the
well, not really, because commits are much less frequent these days.
However yes, IMHO we should have a quick way of updating also core plugins.
Suggestions/help/sponsorship on this are welcome.
All the best.
Why don't we have the core python plugins are git sub modules we can
then host the
Hi all,
I just merged sextante-import branch to master. There is some
work to be done (like running tests and rebuild docs), but SEXTANTE
itself installed and works fine.
Great!
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
Hi
On Fri, Sep 14, 2012 at 11:12 PM, skampus
stefano.cam...@regione.piemonte.it wrote:
does it mean that every change in sextante will be added into qgis master
every time it is released
(almost every night)?
That depends on how the SEXTANTE team chooses to work. Normally new
development
has this migration done? i don't see any new version after 355.
can you indicate which is the new url for svn update?
at the moment it is
http://sextante.googlecode.com/svn/trunk/soft/bindings/qgis-plugin/src/sextante
thank you
--
View this message in context:
Hi all,
We have finally decided to move the SEXTANTE repo (the QGIS part of
it) to the QGIS repository. The Java part will stay in the googlecode
SVN as it is right now.
The repo will be frozen Aug20th, so please commit your changes before
that date. Once the code is migrated, we will update
