Re: [QGIS-Developer] QGIS 3.0 beta

2017-07-13 Thread Rainer Hurling

Am 08.07.2017 um 10:13 schrieb Matthias Kuhn:

Hi all,

Not too far away we will enter feature freeze for QGIS 3.0 and will be
trying to polish the next release as much as possible.

During this time, a lot of testing will need to be done in order to be
able to best spend the bugfixing time. There are a handful of people who
regularly test nightlies and report bugs (thanks!).

I wonder if it's possible to attract more testers for the next release
by providing a "beta".

I think releasing a version labelled "beta" at the beginning of the
feature freeze (and another one half way through) will make more people
aware of the upcoming release. This can lead to additional important
testing from audience which otherwise would only "test" the final
release (with a lower acceptance of bugs). Besides that, I think it will
also be a good signal for devs to start porting plugin code and a very
good preparation for end users marketing-wise.

It will be best served with a blog post explaining how critical the
bugfixing phase is for a release and how resources for this are allocated.

It's just an idea I had in mind for some time. Does anyone dislike it?

Thanks
Matthias


Many thanks for all the work on the upcoming 3.0 version. Really 
appreciated.


As the maintainer of the port for the FreeBSD operating system [1], I am 
in the process of preparing all dependencies for the 3.0 version. Some 
of the needed QT5 and Python3 deps are not present or usable on FreeBSD 
until now. We had good experiences with using 2.x.x versions of QGIS on 
FreeBSD :)


Here my question to the QGIS devs: Is there a (roughly complete) list of 
facultative and optional dependencies and their versions to build and 
run a QGIS 3.0 (beta) on Unix-alike systems? And also, is there a 
(commented) list of options, one can enable/disable at build time?


Any hint or help is really appreciated.

Thanks in advance and greetings from Göttingen in Germany,
Rainer Hurling


[1] http://www.freshports.org/graphics/qgis
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS 3.0 beta

2017-07-09 Thread Tim Sutton
Hi


I would lean towards -1 for a beta - we have had this same debate numerous
times before and tried using beta's before. I don't think a beta will
substantially increase testing uptake and it has the rather bad side effect
that people will be using old code as their reference point (as opposed to
using the nightly builds where they can see the latest fixes at any time).

I'm happy to keep quiet if others think it is worth doing...

Regards

Tim

On Sat, Jul 8, 2017 at 6:50 PM, Jürgen E. Fischer  wrote:

> Hi Richard,
>
> On Sat, 08. Jul 2017 at 12:43:48 +0200, Richard Duivenvoorde wrote:
> > Just for clarity, there IS already a possibility to test/view current
> > master (3.0 development version == 2.99) for Windows users:
> >
> > Either download the latest weekly 2.99 standalone installer from:
> > http://qgis.org/downloads/weekly/
> >
> > OR use
> >
> > OSGeo4W package manager and install the "qgis-dev: QGIS nightly build of
> > the development branch"
>
> OR qgis-full-dev which also depends on a bunch of additional useful
> packages.
>
> > AND to see the most info, ALSO install "qgis-dev-pdb: Debugging symbols
> > for QGIS nightly build of the development branch"
>
> AND now alos on qgis-dev-pdb.   PLUS qgis-full-dev is the base of the
> weekly
> NSIS package.
>
>
> Jürgen
>
> --
> Jürgen E. Fischer   norBIT GmbH Tel.
> +49-4931-918175-31
> Dipl.-Inf. (FH) Rheinstraße 13  Fax.
> +49-4931-918175-50
> Software Engineer   D-26506 Norden
> http://www.norbit.de
> QGIS release manager (PSC)  GermanyIRC: jef on FreeNode
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>



-- 
--
​

Tim Sutton
Visit http://kartoza.com to find out about open source:
 * Desktop GIS programming services
 * Geospatial web development
* GIS Training
* Consulting Services
Skype: timlinux Irc: timlinux on #qgis at freenode.net
Tim is a member of the QGIS Project Steering Committee
---
Kartoza is a merger between Linfiniti and Afrispatial
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS 3.0 beta

2017-07-08 Thread Jürgen E . Fischer
Hi Richard,

On Sat, 08. Jul 2017 at 12:43:48 +0200, Richard Duivenvoorde wrote:
> Just for clarity, there IS already a possibility to test/view current
> master (3.0 development version == 2.99) for Windows users:
> 
> Either download the latest weekly 2.99 standalone installer from:
> http://qgis.org/downloads/weekly/
> 
> OR use
> 
> OSGeo4W package manager and install the "qgis-dev: QGIS nightly build of
> the development branch"

OR qgis-full-dev which also depends on a bunch of additional useful packages.

> AND to see the most info, ALSO install "qgis-dev-pdb: Debugging symbols
> for QGIS nightly build of the development branch"

AND now alos on qgis-dev-pdb.   PLUS qgis-full-dev is the base of the weekly
NSIS package.


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Norden http://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode


signature.asc
Description: PGP signature
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS 3.0 beta

2017-07-08 Thread Richard Duivenvoorde
On 08-07-17 11:48, Wondimagegn Tesfaye wrote:
> Dear Mattias, 
> 
> Thank you for the hard work! This is a good approach. Starting to
> testing the beta before the feature freeze is good to incorporate more
> feedback from the users and developers.

Just for clarity, there IS already a possibility to test/view current
master (3.0 development version == 2.99) for Windows users:

Either download the latest weekly 2.99 standalone installer from:
http://qgis.org/downloads/weekly/

OR use

OSGeo4W package manager and install the "qgis-dev: QGIS nightly build of
the development branch"
AND to see the most info, ALSO install "qgis-dev-pdb: Debugging symbols
for QGIS nightly build of the development branch"

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS 3.0 beta

2017-07-08 Thread Wondimagegn Tesfaye
Dear Mattias,

Thank you for the hard work! This is a good approach. Starting to testing
the beta before the feature freeze is good to incorporate more feedback
from the users and developers.

Regards,
Wondimagegn

On Jul 8, 2017 11:13, "Matthias Kuhn"  wrote:

> Hi all,
>
> Not too far away we will enter feature freeze for QGIS 3.0 and will be
> trying to polish the next release as much as possible.
>
> During this time, a lot of testing will need to be done in order to be
> able to best spend the bugfixing time. There are a handful of people who
> regularly test nightlies and report bugs (thanks!).
>
> I wonder if it's possible to attract more testers for the next release
> by providing a "beta".
>
> I think releasing a version labelled "beta" at the beginning of the
> feature freeze (and another one half way through) will make more people
> aware of the upcoming release. This can lead to additional important
> testing from audience which otherwise would only "test" the final
> release (with a lower acceptance of bugs). Besides that, I think it will
> also be a good signal for devs to start porting plugin code and a very
> good preparation for end users marketing-wise.
>
> It will be best served with a blog post explaining how critical the
> bugfixing phase is for a release and how resources for this are allocated.
>
> It's just an idea I had in mind for some time. Does anyone dislike it?
>
> Thanks
> Matthias
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] QGIS 3.0 beta

2017-07-08 Thread Richard Duivenvoorde
On 08-07-17 10:13, Matthias Kuhn wrote:
> Hi all,
> 
> Not too far away we will enter feature freeze for QGIS 3.0 and will be
> trying to polish the next release as much as possible.
> 
> During this time, a lot of testing will need to be done in order to be
> able to best spend the bugfixing time. There are a handful of people who
> regularly test nightlies and report bugs (thanks!).
> 
> I wonder if it's possible to attract more testers for the next release
> by providing a "beta".
> 
> I think releasing a version labelled "beta" at the beginning of the
> feature freeze (and another one half way through) will make more people
> aware of the upcoming release. This can lead to additional important
> testing from audience which otherwise would only "test" the final
> release (with a lower acceptance of bugs). Besides that, I think it will
> also be a good signal for devs to start porting plugin code and a very
> good preparation for end users marketing-wise.
> 
> It will be best served with a blog post explaining how critical the
> bugfixing phase is for a release and how resources for this are allocated.
> 
> It's just an idea I had in mind for some time. Does anyone dislike it?

Yep, I was thinking about something like this too: BUT there is always
the tension between willing to show and test a new version AND giving
the average user an as stable possible QGIS to work with.
So either work with some beta's OR consider 3.0 (and 3.2?) more or less
as versions which will have some growing pains? Though that is hard to
sell to the average user I think...

Other wild ideas:
- call 3.0 something like: Beta, Troje or Atlantis ;-)

And do a lot of communication that people should really test it in the
actual/real workflows to catch actual usability issues. But also... do
keep in mind that due to the changes in api's, code, Qt, Python etc etc
it is more likely that things will break or crash.

Yesterday I hit the first crash screen (on a Windows machine):

https://files.gitter.im/qgis/QGIS/kjUe/image.png
(ended up as https://issues.qgis.org/issues/16810 by the way)

Nice work, Nathan!

And looking at it, 3.0/beta should probably also have debug info so the
Stack Trace is as descriptive as possible?

Regards,

Richard Duivenvoorde

___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] QGIS 3.0 beta

2017-07-08 Thread Matthias Kuhn
Hi all,

Not too far away we will enter feature freeze for QGIS 3.0 and will be
trying to polish the next release as much as possible.

During this time, a lot of testing will need to be done in order to be
able to best spend the bugfixing time. There are a handful of people who
regularly test nightlies and report bugs (thanks!).

I wonder if it's possible to attract more testers for the next release
by providing a "beta".

I think releasing a version labelled "beta" at the beginning of the
feature freeze (and another one half way through) will make more people
aware of the upcoming release. This can lead to additional important
testing from audience which otherwise would only "test" the final
release (with a lower acceptance of bugs). Besides that, I think it will
also be a good signal for devs to start porting plugin code and a very
good preparation for end users marketing-wise.

It will be best served with a blog post explaining how critical the
bugfixing phase is for a release and how resources for this are allocated.

It's just an idea I had in mind for some time. Does anyone dislike it?

Thanks
Matthias
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer