Anita,
Thanks for pointing out QEP#4, I wasn't aware of it. Tim has done an
impressive work there.
The above-mentioned QEP is a long term thing, what I was suggesting is a
very short term (i.e. 2 cycles) proposal to try and satisfy the current
needs for stability and devlopment momentum. I also
Thank you for your comments
I did not mean to exclude all C++ tests. If somebody wants or needs to
write tests in C++ please continue to do so.
I am referring only the ones that duplicate python tests. I don't think
they have additional value and make maintainability harder. In general I
think
On Mon, Nov 10, 2014 at 5:57 AM, Geo DrinX geodr...@gmail.com wrote:
Yes yes yes.
+1
but also +999 :)
And why not + ?
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
On Mon, Nov 10, 2014 at 3:23 PM, Luca Manganelli luc...@gmail.com wrote:
On Mon, Nov 10, 2014 at 5:57 AM, Geo DrinX geodr...@gmail.com wrote:
Yes yes yes.
+1
but also +999 :)
And why not + ?
Seeing this I can't resist to quote a bit of PEP-10 [1]
+1 I like it
+0 I don't care,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 10/11/2014 09:31, Martin Dobias ha scritto:
really valued much beyond the above scores, but it's nice to see
people get excited about such geeky stuff.
Hi all,
I hate cooling down the enthusiasm, but I really see LTS as an empty
word. To me,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 10/11/2014 04:56, Minoru Akagi ha scritto:
Please open a ticket if you like.
done, thanks.
all the best.
- --
Paolo Cavallini - www.faunalia.eu
QGIS PostGIS courses: http://www.faunalia.eu/training.html
-BEGIN PGP SIGNATURE-
Version:
I have an inexperienced QGIS user who needed to draw some simple line strings.
She created a new shapefile layer (line type), enabled editing and used the
Add Feature button to draw a line string.
- She didn't right click to finished the feature when she was done!
She saved the
On Mon, Nov 10, 2014 at 9:42 AM, Paolo Cavallini cavall...@faunalia.it wrote:
To me, the whole issue boils down to having resources to do
serious backporting of fixes. Without that, LTS will have no practical
effect, as users will use the latest, more bugfixed version.
more bugfixed is not
On Mon, Nov 10, 2014 at 10:42:42AM +0100, Luca Manganelli wrote:
So, I believe that in production environment the most stable (!=
latest) version is used. For almost 2 years we used 1.7.4, for me the
most stable QGIS version in earth (more than 2.4 and 2.6!).
Yep, that little third number in
So, I believe that in production environment the most stable (!=
latest) version is used. For almost 2 years we used 1.7.4, for me the
most stable QGIS version in earth (more than 2.4 and 2.6!).
Oh man. I couldn't even use 1.7.4 anymore it's so old ;)
Anyway the point is a valid one. Running
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 10/11/2014 10:42, Luca Manganelli ha scritto:
So, I believe that in production environment the most stable (!=
latest) version is used. For almost 2 years we used 1.7.4, for me
the most stable QGIS version in earth (more than 2.4 and 2.6!).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 10/11/2014 10:56, Nathan Woodrow ha scritto:
IMO we don't need resources to do bug fixing. The dev that does
the bug fix in master can do it in the 2.x branch for that stable
release if
Sorry I do not agree here: we had many cases of fixes
Hi Paolo and all developers,
Il 10/11/2014 09.42, Paolo Cavallini ha scritto:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 10/11/2014 09:31, Martin Dobias ha scritto:
really valued much beyond the above scores, but it's nice to see
people get excited about such geeky stuff.
Hi all,
I
On Mon, Nov 10, 2014 at 09:56:22AM +, Nathan Woodrow wrote:
relevant.. This obviously has to be done smart but using the recent crash
and project corruption as an example that Martin fixed right away, to me
this warrants a new release off that branch, LTS or not, as project
corruption is
Hi all,
QEP #4 allows to do backports for every release. Not only LTR. 2.6.1
will be very welcome.
LTR releases will be available for 1 year and will receive bugfixes
during that time. That's not going to happen magically. That requires
power users and organizations to help the development.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all.
I noticed that import gdalconst fails on current win version (2.6,
gdal 1.11), whereas it is ok on Debian (2.6, gdal 1.10.1): has
something changed, or is this a (packaging?) issue?
All the best.
- --
Paolo Cavallini - www.faunalia.eu
QGIS
Dear all,
i'm testing qgis-server 2.6.0 with lizmap web client on ubuntu 12.04
server
and qgis server crashes trying to print a vector layer with advanced
symbols
( line pattern fill and marker line); apache log following:
# apache2 error.log
#mod_fcgid: error reading data, FastCGI
2014-11-10 11:40 GMT+01:00 Roy royr...@outlook.com:
Dear all,
i'm testing qgis-server 2.6.0 with lizmap web client on ubuntu 12.04
server
and qgis server crashes trying to print a vector layer with advanced
symbols
( line pattern fill and marker line); apache log following:
# apache2
Il 10/11/2014 11.44, Alessandro Pasotti ha scritto:
2014-11-10 11:40 GMT+01:00 Roy royr...@outlook.com:
Dear all,
i'm testing qgis-server 2.6.0 with lizmap web client on ubuntu 12.04
server
and qgis server crashes trying to print a vector layer with advanced
symbols
( line pattern fill and
A couple of thoughts from a non-dev looking inwards:
Sorry I do not agree here: we had many cases of fixes breaking other stuff
Would not something like Unit Tests help ameliorate that? That's what they're
designed for isn't it? I realise the state of QGIS' unit test infrastructure
isn't
Personally I’d think there are two bugs here, at least from a user-interface
perspective, even if they’re not from a technical one:
a) Edits showing when editing was disabled (I’ve seen this one myself).
b)No warning that the edited features hadn’t been “finished” when saving
and/or
b)No warning that the edited features hadn’t been “finished” when
saving and/or when disabling editing.
(2.6 Testing indicates that disabling and then re-enabling editing while
editing but not “finishing” a feature shows that you continue editing the
same feature; I’m not sure that’s very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all.
Il 10/11/2014 13:13, Jonathan Moules ha scritto:
Then why not fix the bugs and require them to be backported? I
know that seems flippant, but is there a reason that backporting by
the submitter/committer can't be required for any bugfix
b)No warning that the edited features hadn’t been “finished” when saving
and/or when disabling editing.
I have created a ticket for this: http://hub.qgis.org/issues/11607
(2.6 Testing indicates that disabling and then re-enabling editing while
editing but not “finishing” a feature
Hi,
Irrespective of which is the way to do it (I lean toward checking it when
there's a selection), I'd suggest that the behaviour should be consistent. So
either this default be changed, or the field calculator one be, otherwise you
end up with confused users.
Cheers,
Jonathan
-Original
Hi,
Is there an ETA on this? We're thinking of moving up to 2.6, but I can see this
hitting us if we do.
Thanks,
Jonathan
-Original Message-
From: qgis-developer-boun...@lists.osgeo.org
[mailto:qgis-developer-boun...@lists.osgeo.org] On Behalf Of Paolo Cavallini
Sent: Saturday, November
Hi,
I think that functionality that works on selections and not on the whole
layer should always be optional, and not the default.
And yes - consistency would be nice ;-)
Thanks,
Andreas
On 10.11.2014 15:48, Jonathan Moules wrote:
Hi,
Irrespective of which is the way to do it (I lean
Hi Andreas
On 2014/11/08 18:34, Andreas Neumann wrote:
Hi Zoltan,
There are many other file formats besides shapes, including many
databases. So people should stop thinking that the universe only
circles around shapefiles.
Yes. I know. That's exactly what I am banging my head about.
Do you
thank you Martin
regards, Luigi Pirelli
On 7 November 2014 18:55, Martin Dobias wonder...@gmail.com wrote:
On Tue, Nov 4, 2014 at 1:53 AM, Luigi Pirelli lui...@gmail.com wrote:
Hi martin
I almost agree, but qgis is not only a lib but kind of framework. It's
use is different tespect the use
29 matches
Mail list logo
