Hi Tim
- release now
+1
Regards,
Marco
Am Montag, 30. Mai 2011, 21.53:31 schrieb Tim Sutton:
Hi Borys
On Mon, May 30, 2011 at 7:41 PM, Borys Jurgiel li...@borysjurgiel.pl
wrote:
Dnia poniedziałek, 30 maja 2011 o 11:15:23 Jürgen E. Fischer napisał(a):
Hi Borys,
On Mon, 30. May
On Tue, 31 May 2011 09:30:25 +0200, Paolo Cavallini wrote:
Hi all.
Am I the only one to feel uncomfortable releasing 1.7 with 60 bugs
classified as blocking?
https://trac.osgeo.org/qgis/report/16
IMVHO we should examine them, and either reclassify them or solve
them
before release. My feeling
+1 for me for Paolos suggestion ..
I think releasing 1.7 with a lot of bugs and instability will bring us
no friends ..
reclassify and/or solve at least a lot of them would be very cool
(from usersight)
So if i can help just drop me a note - it's just i think i cannot help
solving the bugs ;)
I think releasing as a beta would be a good idea, that way we get 1.7
release out but users know it's not fully done. This way it also gives us
more time to do bug fixing.
- Nathan
On Tue, May 31, 2011 at 6:16 PM, Werner Macho werner.ma...@gmail.comwrote:
+1 for me for Paolos suggestion ..
I
On Tue, May 31, 2011 at 06:23:49PM +1000, Nathan Woodrow wrote:
I think releasing as a beta would be a good idea, that way we get 1.7
release out but users know it's not fully done. This way it also gives us
more time to do bug fixing.
I agree with this. A beta would be fine, possibly
I share your concern but no one has actually the time or manpower to
solve these bugs, and to be honest I don't think that postponing the
release any longer will improve the situation. This release has enough
good points to compensate, I hope all this shiny stuff will blind the
users enough so
wow
+1 for me on that ..
a really good idea .. beta + call for funding to solve last bugs ..
in that way some companys will probably see that there is a lot of
work and time invested in opensource and it would be nice to bring us
all ahead by supporting qgis .. we do not have licence issues :)
Hi,
I agree with Paolo's concerns, and I also believe that ordinary users
can benefit from testing the 1.7.0. In addition, they may find a few
more blocking bugs... which ultimately may help the community provide an
even better version.
So +1 for a beta release.
Mayeul
Le mardi 31 mai 2011 à
+1 for release as a beta.
I share Paolo's unease about a full release with 60 major bugs. It takes
much more effort to build a good reputation than to loose one.
In the documentation, we are quick to highlight new tools and enhancements,
but how about adding something on Known Issues and
Hi,
+1 for beta release. I really appreciate bug fixing approach.
Pavol
Dňa 31.05.2011 11:01, Mayeul Kauffmann wrote / napísal(a):
Hi,
I agree with Paolo's concerns, and I also believe that ordinary users
can benefit from testing the 1.7.0. In addition, they may find a few
more blocking
On Tue, 31 May 2011 10:04:31 +0100, Andrew Chapman
andrew.chap...@donkagen.co.uk wrote:
+1 for release as a beta.
agreed - I think it is a good compromise.
It is also ok asking for sponsorship to fix bugs, but most people have
no
way of knowing what sort of sums would make a difference. Or is
qgis-developer-boun...@lists.osgeo.org scritti il 31/05/2011 10.42.36
wow
+1 for me on that ..
a really good idea .. beta + call for funding to solve last bugs ..
in that way some companys will probably see that there is a lot of
work and time invested in opensource and it would be nice to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/31/2011 09:30 AM, Paolo Cavallini wrote:
Hi all.
Am I the only one to feel uncomfortable releasing 1.7 with 60 bugs
classified as blocking?
https://trac.osgeo.org/qgis/report/16
IMVHO we should examine them, and either reclassify them or
Hello allanlumte,
allanlumte lumte...@gmail.com, [20110526 - 14:35:44]
From an arcpy approach
http://geoscripting.blogspot.com/2011/05/exporting-current-arcmap-document.html
Mxd2Qgs tool can export arcmap layers to a qgs project file.
Good thing that qgs files are take xml format.
Cool
At least in raster clipping, I cannot set -32768 as NULL using the
gui, cannot write the -
I get
gdalwarp -dstnodata 32768 -q -cutline
/media/Iomega_HDD/FLUXPYR/FlxPyrAOI1/FlxPyrAOI1.shp -dstalpha -of
GTiff /media/Iomega_HDD/FLUXPYR/SRTM/SRTM90v41/srtm36y37_04.tif
On 05/31/2011 05:35 PM, Marco Hugentobler wrote:
Hi all
I'm in favour of releasing 1.7 now. The release was already planned for March
and was shifted then. There will always be a large number of bugs in the
queue, even with donations. Maybe we even discover more of them in a beta
version :-)
Ciao Paolo, all,
I am loosely following the list (sometimes) but found this one
rather striking:
From jr.morre...@enoreth.net
On Tue, 31 May 2011 09:30:25 +0200, Paolo Cavallini wrote:
Hi all.
Am I the only one to feel uncomfortable releasing 1.7 with 60 bugs
classified as blocking?
Me as
Dear QGIS developer,
i am not a QGIS developer but would add my 2c too. :)
I completely share the opinion of Markus and Paolo. Please do not
release QGIS with 60 blocker bugs left even as a beta release.
This will disappoint many user who are willingly to test the new
features and the usability
Hi Marco,
On Tue, 31. May 2011 at 16:35:19 +0200, Marco Hugentobler wrote:
I'm in favour of releasing 1.7 now. The release was already planned for March
and was shifted then. There will always be a large number of bugs in the
queue, even with donations. Maybe we even discover more of them in
On 05/31/2011 02:07 PM, Jürgen E. Fischer wrote:
Hi Marco,
On Tue, 31. May 2011 at 16:35:19 +0200, Marco Hugentobler wrote:
I'm in favour of releasing 1.7 now. The release was already planned for
March
and was shifted then. There will always be a large number of bugs in the
queue, even
20 matches
Mail list logo
