Re: [QGIS-Developer] Where do we sit with respect to release?

[Paolo Cavallini]

Il 10/01/2018 13:03, Tim Sutton ha scritto:

> Thanks for your suggestion - we discussed this at the PSC meeting on
> Monday night and Paolo Cavallini  is going to be putting together a
> resource page for plugins developers and then putting out a call for
> them to start their plugin migration work.

In fact, I have already set up the page:
https://github.com/qgis/QGIS/wiki/Plugin-migration-to-QGIS-3
Please help me filling it up.
All the best.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis
___
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] Where do we sit with respect to release?

[Tim Sutton]

Hi Olivier

Thanks for your suggestion - we discussed this at the PSC meeting on Monday 
night and Paolo Cavallini  is going to be putting together a resource page for 
plugins developers and then putting out a call for them to start their plugin 
migration work.

Regards

Tim

> On 10 Jan 2018, at 10:34, Olivier Dalang  wrote:
> 
> +1 for more stable release even if it's a few more weeks
> 
> If feature freeze is confirmed, I would also suggest to send an email to all 
> plugin devs to say that no plugin will work anymore and to give some pointers 
> as to how to migrate the plugins to python/qgis 3. Most devs are probably 
> well aware of upcomming QGIS3, but this may still wake up some of us, and 
> centralizing the info about how to migrate to QGIS3 would be nice for all of 
> us anyway.
> 
> Another email to both dev and uses mailing lists to encourage people to test 
> extensively with actual projects and to remind people on best practices to 
> report bugs (especially concerning whether a bug should be flagged as blocker 
> or not) would also probably be very useful to have better feedback from 
> testing.
> 
> Thank you very much and happy new year :)
> 
> Olivier
> 
> 
> On Wed, Jan 10, 2018 at 8:45 PM, Tom Chadwin  > wrote:
> I know there is excitement, and I'm sure all the devs want the release done.
> However, I think Juergen's proposal is the best (release 23 Feb):
> 
> - more debugging time
> - tallies with established release cycle
> - respects the advice and plans of the Release Manager
> 
> I 100% prioritise stability over early release. As you know, I'm not a QGIS
> dev, so I'm speaking to you both as a user and as the manager of an
> organization's installation base (about 30 seats).
> 
> Yes, I know you will say we have LTR, but a significant aim of the QGIS
> project is to increase our user base. As Nyall says, many people will hear
> about the 3 release and try QGIS out. Stability is absolutely critical for
> those first-timers. Their point of comparison is everyone's favourite
> proprietary GIS. I imagine they also prioritise stability.
> 
> Hope this makes sense
> 
> Tom
> 
> 
> 
> -
> Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html 
> 
> ___
> 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

—







Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

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

___
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] Where do we sit with respect to release?

[G. Allegri]

Thanks everyone for the great work!
As a power user, plugin developer and (Q)GIS teacher (I face dozens of
professional users frequently) I'm totally in favour to post-pone release
and gain reliability and stability.

I don't think there's such a compulsive need to release sooner. Release
often, release soon, will probably be necessary for the next minors (bug
fixing).

@Denis I was worried as you, but I believe an Osgeo4W user is a kind of
user with enough skills to manage the switch. Most users will probably use
the standalone installer I guess.

giovanni



Il 10 gen 2018 09:35, "Olivier Dalang"  ha
scritto:

> +1 for more stable release even if it's a few more weeks
>
> If feature freeze is confirmed, I would also suggest to send an email to
> all plugin devs to say that no plugin will work anymore and to give some
> pointers as to how to migrate the plugins to python/qgis 3. Most devs are
> probably well aware of upcomming QGIS3, but this may still wake up some of
> us, and centralizing the info about how to migrate to QGIS3 would be nice
> for all of us anyway.
>
> Another email to both dev and uses mailing lists to encourage people to
> test extensively with actual projects and to remind people on best
> practices to report bugs (especially concerning whether a bug should be
> flagged as blocker or not) would also probably be very useful to have
> better feedback from testing.
>
> Thank you very much and happy new year :)
>
> Olivier
>
>
> On Wed, Jan 10, 2018 at 8:45 PM, Tom Chadwin 
> wrote:
>
>> I know there is excitement, and I'm sure all the devs want the release
>> done.
>> However, I think Juergen's proposal is the best (release 23 Feb):
>>
>> - more debugging time
>> - tallies with established release cycle
>> - respects the advice and plans of the Release Manager
>>
>> I 100% prioritise stability over early release. As you know, I'm not a
>> QGIS
>> dev, so I'm speaking to you both as a user and as the manager of an
>> organization's installation base (about 30 seats).
>>
>> Yes, I know you will say we have LTR, but a significant aim of the QGIS
>> project is to increase our user base. As Nyall says, many people will hear
>> about the 3 release and try QGIS out. Stability is absolutely critical for
>> those first-timers. Their point of comparison is everyone's favourite
>> proprietary GIS. I imagine they also prioritise stability.
>>
>> Hope this makes sense
>>
>> Tom
>>
>>
>>
>> -
>> Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
>> --
>> Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.
>> html
>> ___
>> 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
>
___
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] Where do we sit with respect to release?

[Olivier Dalang]

+1 for more stable release even if it's a few more weeks

If feature freeze is confirmed, I would also suggest to send an email to
all plugin devs to say that no plugin will work anymore and to give some
pointers as to how to migrate the plugins to python/qgis 3. Most devs are
probably well aware of upcomming QGIS3, but this may still wake up some of
us, and centralizing the info about how to migrate to QGIS3 would be nice
for all of us anyway.

Another email to both dev and uses mailing lists to encourage people to
test extensively with actual projects and to remind people on best
practices to report bugs (especially concerning whether a bug should be
flagged as blocker or not) would also probably be very useful to have
better feedback from testing.

Thank you very much and happy new year :)

Olivier


On Wed, Jan 10, 2018 at 8:45 PM, Tom Chadwin 
wrote:

> I know there is excitement, and I'm sure all the devs want the release
> done.
> However, I think Juergen's proposal is the best (release 23 Feb):
>
> - more debugging time
> - tallies with established release cycle
> - respects the advice and plans of the Release Manager
>
> I 100% prioritise stability over early release. As you know, I'm not a QGIS
> dev, so I'm speaking to you both as a user and as the manager of an
> organization's installation base (about 30 seats).
>
> Yes, I know you will say we have LTR, but a significant aim of the QGIS
> project is to increase our user base. As Nyall says, many people will hear
> about the 3 release and try QGIS out. Stability is absolutely critical for
> those first-timers. Their point of comparison is everyone's favourite
> proprietary GIS. I imagine they also prioritise stability.
>
> Hope this makes sense
>
> Tom
>
>
>
> -
> Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-
> f4099106.html
> ___
> 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] Where do we sit with respect to release?

[Alexander Bruy]

On 9 January 2018 at 23:21, Jürgen E. Fischer  wrote:
> Hi Matthias,
>
> On Tue, 09. Jan 2018 at 12:31:32 +0100, Matthias Kuhn wrote:
>> On 01/09/2018 11:21 AM, Mathieu Pellerin wrote:
>> > > Also for the bug fixing, lets give it a full month
>> >
>> > If the project settled on Feb. 8, can we have an official
>> > acknowledgement on this? Maybe a simple mail to the dev list stating
>> > "QGIS 3.0 will be released on Feb. 8, 2018".
>
>> Feb 8 sounds like a sensible date to me, some time left for fixing but
>> still in a reasonable timeframe.
>
> I'd opt for the next set point release dates.  19.1. is probably to early, so
> 23.2. would be up next.
>
> 3.0.0 would be release then. 2.14.22 would be the last release of the old LTR
> on 19.1. and would be replaced by 2.18.17 when 3.0.0 is released.

+1 for this timeline. This will allow us to fix more bugs and provide users
with more stable 3.0 release.

-- 
Alexander Bruy
___
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] Where do we sit with respect to release?

[Tom Chadwin]

I know there is excitement, and I'm sure all the devs want the release done.
However, I think Juergen's proposal is the best (release 23 Feb):

- more debugging time
- tallies with established release cycle
- respects the advice and plans of the Release Manager

I 100% prioritise stability over early release. As you know, I'm not a QGIS
dev, so I'm speaking to you both as a user and as the manager of an
organization's installation base (about 30 seats). 

Yes, I know you will say we have LTR, but a significant aim of the QGIS
project is to increase our user base. As Nyall says, many people will hear
about the 3 release and try QGIS out. Stability is absolutely critical for
those first-timers. Their point of comparison is everyone's favourite
proprietary GIS. I imagine they also prioritise stability.

Hope this makes sense

Tom



-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon 
--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html
___
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] Where do we sit with respect to release?

[Nyall Dawson]

On 9 January 2018 at 23:21, Jürgen E. Fischer  wrote:
> Hi Matthias,
>
> On Tue, 09. Jan 2018 at 12:31:32 +0100, Matthias Kuhn wrote:
>> On 01/09/2018 11:21 AM, Mathieu Pellerin wrote:
>> > > Also for the bug fixing, lets give it a full month
>> >
>> > If the project settled on Feb. 8, can we have an official
>> > acknowledgement on this? Maybe a simple mail to the dev list stating
>> > "QGIS 3.0 will be released on Feb. 8, 2018".
>
>> Feb 8 sounds like a sensible date to me, some time left for fixing but
>> still in a reasonable timeframe.
>
> I'd opt for the next set point release dates.  19.1. is probably to early, so
> 23.2. would be up next.
>
> 3.0.0 would be release then. 2.14.22 would be the last release of the old LTR
> on 19.1. and would be replaced by 2.18.17 when 3.0.0 is released.
>

I like this timeline. We've got a LOT of work to do to bring stability
to 3.0, and I'd prefer for users to have a great first impression of
this release.

Given how big a release it is, we're going to get a lot of new and
return users (who have previously used and moved away from QGIS)
installing and evaluating 3.0. For the sake of a couple of weeks I'd
prefer squash a few more of these bugs and give a great initial
impression of QGIS 3.0 to these users.

Nyall
___
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] Where do we sit with respect to release?

[Denis Rouzaud]

I'm just wondering if it makes sense to release a new major version under
the same "branches".

If I take Qt's example, there's 2 distinct package name.

But if it's just me who is worried about such a change, then forget about
it.

Le mar. 9 janv. 2018 à 15:38, Jürgen E. Fischer  a écrit :

> Hi Denis,
>
> On Tue, 09. Jan 2018 at 19:21:28 +, Denis Rouzaud wrote:
> > To my understanding: if you have 2.18.x in Osgeo4W, it's not the LTR. And
> > this branch will then receive 3.0
> >
> > So to keep 2.18.x, one will have to check a new entry in Osgeo4W
> installer.
>
> qgis-ltr is the current ltr that is not also the current release (ie.
> never a
> brand new release),
> qgis is the current release,
> qgis-dev is current master.
>
> Version numbers change - that definition doesn't.
>
>
> 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
___
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] Where do we sit with respect to release?

[Jürgen E . Fischer]

Hi Denis,

On Tue, 09. Jan 2018 at 19:21:28 +, Denis Rouzaud wrote:
> To my understanding: if you have 2.18.x in Osgeo4W, it's not the LTR. And
> this branch will then receive 3.0
> 
> So to keep 2.18.x, one will have to check a new entry in Osgeo4W installer.

qgis-ltr is the current ltr that is not also the current release (ie. never a
brand new release),
qgis is the current release,
qgis-dev is current master.

Version numbers change - that definition doesn't.


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] Where do we sit with respect to release?

[Jürgen E . Fischer]

Hi Andreas,

On Tue, 09. Jan 2018 at 20:17:00 +0100, Andreas Neumann wrote:
> As to my understanding, 2.18 is not automatically replaced by 3.x
> 
> 2.18 will remain LTR until 3.6 is released, because 3.4 will be the next LTR
> - right Jürgen?

qgis-ltr in OSGeo4W is 2.14.  qgis is 2.18.  qgis-dev is 2.99.

When 3.0 is released:

qgis-ltr will be 2.18.  qgis will be 3.0  and qgis-dev will be 3.1.

Just like one every other release that follows an ltr release.

Same for the debian/ubuntu repositories:

debian-ltr currently carries 2.14
debian carries 2.18
debian-nightly carries 2.99

After the 3.0 release .0:

debian-ltr will have 2.18
debian will have 3.0
debian-nightly 3.1


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] Where do we sit with respect to release?

[Denis Rouzaud]

To my understanding: if you have 2.18.x in Osgeo4W, it's not the LTR. And
this branch will then receive 3.0

So to keep 2.18.x, one will have to check a new entry in Osgeo4W installer.



Le mar. 9 janv. 2018 à 15:17, Andreas Neumann  a
écrit :

> Hi Denis,
>
> As to my understanding, 2.18 is not automatically replaced by 3.x
>
> 2.18 will remain LTR until 3.6 is released, because 3.4 will be the next
> LTR - right Jürgen?
>
> Andreas
>
> On 09.01.2018 20:14, Denis Rouzaud wrote:
>
> Am I the only one thinking it's not a good idea that 2.18.x is
> automatically replaced by 3.x ?
>
>
>
>
>
> Le mar. 9 janv. 2018 à 10:33, Jürgen E. Fischer  a écrit :
>
>> Hi Denis,
>>
>> On Tue, 09. Jan 2018 at 14:19:21 +, Denis Rouzaud wrote:
>> > I'm just wondering how it will happen for windows users using Osgeo4W
>> > installer.
>> >
>> > I think we should avoid that a user having the last non LTR release
>> > (2.18.x) gets automatically updated to 3.0 and would have to install
>> LTR to
>> > get his 2.18.x available again on his system.
>>
>> 2.18 is not even a non LTR release.
>>
>> > Jürgen, am I missing something?
>>
>> No, that's what's going to happen.
>>
>>
>> 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
>
>
>
> ___
> QGIS-Developer mailing listqgis-develo...@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
___
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] Where do we sit with respect to release?

[Andreas Neumann]

Hi Denis,

As to my understanding, 2.18 is not automatically replaced by 3.x

2.18 will remain LTR until 3.6 is released, because 3.4 will be the next 
LTR - right Jürgen?


Andreas


On 09.01.2018 20:14, Denis Rouzaud wrote:
Am I the only one thinking it's not a good idea that 2.18.x is 
automatically replaced by 3.x ?






Le mar. 9 janv. 2018 à 10:33, Jürgen E. Fischer > a écrit :


Hi Denis,

On Tue, 09. Jan 2018 at 14:19:21 +, Denis Rouzaud wrote:
> I'm just wondering how it will happen for windows users using
Osgeo4W
> installer.
>
> I think we should avoid that a user having the last non LTR release
> (2.18.x) gets automatically updated to 3.0 and would have to
install LTR to
> get his 2.18.x available again on his system.

2.18 is not even a non LTR release.

> Jürgen, am I missing something?

No, that's what's going to happen.


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)  Germany IRC: 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



___
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] Where do we sit with respect to release?

[Denis Rouzaud]

Am I the only one thinking it's not a good idea that 2.18.x is
automatically replaced by 3.x ?





Le mar. 9 janv. 2018 à 10:33, Jürgen E. Fischer  a écrit :

> Hi Denis,
>
> On Tue, 09. Jan 2018 at 14:19:21 +, Denis Rouzaud wrote:
> > I'm just wondering how it will happen for windows users using Osgeo4W
> > installer.
> >
> > I think we should avoid that a user having the last non LTR release
> > (2.18.x) gets automatically updated to 3.0 and would have to install LTR
> to
> > get his 2.18.x available again on his system.
>
> 2.18 is not even a non LTR release.
>
> > Jürgen, am I missing something?
>
> No, that's what's going to happen.
>
>
> 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
___
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] Where do we sit with respect to release?

[Jürgen E . Fischer]

Hi Denis,

On Tue, 09. Jan 2018 at 14:19:21 +, Denis Rouzaud wrote:
> I'm just wondering how it will happen for windows users using Osgeo4W
> installer.
> 
> I think we should avoid that a user having the last non LTR release
> (2.18.x) gets automatically updated to 3.0 and would have to install LTR to
> get his 2.18.x available again on his system.

2.18 is not even a non LTR release.

> Jürgen, am I missing something?

No, that's what's going to happen.


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] Where do we sit with respect to release?

[Denis Rouzaud]

I'm just wondering how it will happen for windows users using Osgeo4W
installer.

I think we should avoid that a user having the last non LTR release
(2.18.x) gets automatically updated to 3.0 and would have to install LTR to
get his 2.18.x available again on his system.

Jürgen, am I missing something?


Le mar. 9 janv. 2018 à 10:11, Yves Jacolin  a écrit :

> +1 to this proposition. I am sure this will be done this way finally. We
> are sure to find some issue and needs a new release soon after the 1st
> release. Release often ... :)
>
> Y.
>
> Le 09/01/2018 à 14:57, Denis Rouzaud a écrit :
>
>
> Just saying...
>
> We could release 3.0.0 on Feb 8, then 3.0.1 on Feb 23 and follow the
> regular path afterwards.
> I think having a first bugfix release 2 weeks after the official release
> makes a lot of sense...
>
> My 2 cents.
>
> Le mar. 9 janv. 2018 à 09:40, Andreas Neumann  a
> écrit :
>
>> Cool, excitement and anticipation is good - then they can all test PRIOR
>> ! to the release (the nightlies and weeklies) and help make the
>> release better!
>>
>> We did not promise any date. We should release when we think it is in a
>> good shape.
>>
>> Andreas
>>
>> On 2018-01-09 14:33, Mathieu Pellerin wrote:
>>
>> Hmm a choice between too early and "too late", ;)
>>
>> While a sync with ongoing point release would be nice, Feb 23 seems
>> really far down the road. I think there's an expectation we'd release
>> sooner. At least, there's a lot of excitement and anticipation.
>>
>> M
>>
>> On Jan 9, 2018 20:22, "Jürgen E. Fischer"  wrote:
>>
>>> Hi Matthias,
>>>
>>> On Tue, 09. Jan 2018 at 12:31:32 +0100, Matthias Kuhn wrote:
>>> > On 01/09/2018 11:21 AM, Mathieu Pellerin wrote:
>>> > > > Also for the bug fixing, lets give it a full month
>>> > >
>>> > > If the project settled on Feb. 8, can we have an official
>>> > > acknowledgement on this? Maybe a simple mail to the dev list stating
>>> > > "QGIS 3.0 will be released on Feb. 8, 2018".
>>>
>>> > Feb 8 sounds like a sensible date to me, some time left for fixing but
>>> > still in a reasonable timeframe.
>>>
>>> I'd opt for the next set point release dates.  19.1. is probably to
>>> early, so
>>> 23.2. would be up next.
>>>
>>> 3.0.0 would be release then. 2.14.22 would be the last release of the
>>> old LTR
>>> on 19.1. and would be replaced by 2.18.17 when 3.0.0 is released.
>>>
>>>
>>> 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
>>
>>
>> ___
>> 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
>
>
>
> ___
> QGIS-Developer mailing listqgis-develo...@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> -- http://yjacolin.gloobe.org
>
> ___
> 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] Where do we sit with respect to release?

[Yves Jacolin]

+1 to this proposition. I am sure this will be done this way finally. We
are sure to find some issue and needs a new release soon after the 1st
release. Release often ... :)

Y.


Le 09/01/2018 à 14:57, Denis Rouzaud a écrit :
>
> Just saying...
>
> We could release 3.0.0 on Feb 8, then 3.0.1 on Feb 23 and follow the
> regular path afterwards.
> I think having a first bugfix release 2 weeks after the official
> release makes a lot of sense...
>
> My 2 cents.
>
> Le mar. 9 janv. 2018 à 09:40, Andreas Neumann  > a écrit :
>
> Cool, excitement and anticipation is good - then they can all test
> PRIOR ! to the release (the nightlies and weeklies) and
> help make the release better!
>
> We did not promise any date. We should release when we think it is
> in a good shape.
>
> Andreas
>
> On 2018-01-09 14:33, Mathieu Pellerin wrote:
>
>> Hmm a choice between too early and "too late", ;)
>>  
>> While a sync with ongoing point release would be nice, Feb 23
>> seems really far down the road. I think there's an expectation
>> we'd release sooner. At least, there's a lot of excitement and
>> anticipation.
>>  
>> M
>>
>> On Jan 9, 2018 20:22, "Jürgen E. Fischer" > > wrote:
>>
>> Hi Matthias,
>>
>> On Tue, 09. Jan 2018 at 12:31:32 +0100, Matthias Kuhn wrote:
>> > On 01/09/2018 11:21 AM, Mathieu Pellerin wrote:
>> > > > Also for the bug fixing, lets give it a full month
>> > >
>> > > If the project settled on Feb. 8, can we have an official
>> > > acknowledgement on this? Maybe a simple mail to the dev
>> list stating
>> > > "QGIS 3.0 will be released on Feb. 8, 2018".
>>
>> > Feb 8 sounds like a sensible date to me, some time left for
>> fixing but
>> > still in a reasonable timeframe.
>>
>> I'd opt for the next set point release dates.  19.1. is
>> probably to early, so
>> 23.2. would be up next.
>>
>> 3.0.0 would be release then. 2.14.22 would be the last
>> release of the old LTR
>> on 19.1. and would be replaced by 2.18.17 when 3.0.0 is released.
>>
>>
>> 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)  Germany                    IRC:
>> 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
>>
>>
>> ___
>> 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
>
>
>
> ___
> 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

-- 
http://yjacolin.gloobe.org

___
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] Where do we sit with respect to release?

[Régis Haubourg]

+1 with Denis,
in the past releases, we have had at least twice that scenario.
Régis

2018-01-09 14:57 GMT+01:00 Denis Rouzaud :

>
> Just saying...
>
> We could release 3.0.0 on Feb 8, then 3.0.1 on Feb 23 and follow the
> regular path afterwards.
> I think having a first bugfix release 2 weeks after the official release
> makes a lot of sense...
>
> My 2 cents.
>
> Le mar. 9 janv. 2018 à 09:40, Andreas Neumann  a
> écrit :
>
>> Cool, excitement and anticipation is good - then they can all test PRIOR
>> ! to the release (the nightlies and weeklies) and help make the
>> release better!
>>
>> We did not promise any date. We should release when we think it is in a
>> good shape.
>>
>> Andreas
>>
>> On 2018-01-09 14:33, Mathieu Pellerin wrote:
>>
>> Hmm a choice between too early and "too late", ;)
>>
>> While a sync with ongoing point release would be nice, Feb 23 seems
>> really far down the road. I think there's an expectation we'd release
>> sooner. At least, there's a lot of excitement and anticipation.
>>
>> M
>>
>> On Jan 9, 2018 20:22, "Jürgen E. Fischer"  wrote:
>>
>>> Hi Matthias,
>>>
>>> On Tue, 09. Jan 2018 at 12:31:32 +0100, Matthias Kuhn wrote:
>>> > On 01/09/2018 11:21 AM, Mathieu Pellerin wrote:
>>> > > > Also for the bug fixing, lets give it a full month
>>> > >
>>> > > If the project settled on Feb. 8, can we have an official
>>> > > acknowledgement on this? Maybe a simple mail to the dev list stating
>>> > > "QGIS 3.0 will be released on Feb. 8, 2018".
>>>
>>> > Feb 8 sounds like a sensible date to me, some time left for fixing but
>>> > still in a reasonable timeframe.
>>>
>>> I'd opt for the next set point release dates.  19.1. is probably to
>>> early, so
>>> 23.2. would be up next.
>>>
>>> 3.0.0 would be release then. 2.14.22 would be the last release of the
>>> old LTR
>>> on 19.1. and would be replaced by 2.18.17 when 3.0.0 is released.
>>>
>>>
>>> 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
>>
>>
>> ___
>> 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
>
>
> ___
> 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] Where do we sit with respect to release?

[Denis Rouzaud]

Just saying...

We could release 3.0.0 on Feb 8, then 3.0.1 on Feb 23 and follow the
regular path afterwards.
I think having a first bugfix release 2 weeks after the official release
makes a lot of sense...

My 2 cents.

Le mar. 9 janv. 2018 à 09:40, Andreas Neumann  a
écrit :

> Cool, excitement and anticipation is good - then they can all test PRIOR
> ! to the release (the nightlies and weeklies) and help make the
> release better!
>
> We did not promise any date. We should release when we think it is in a
> good shape.
>
> Andreas
>
> On 2018-01-09 14:33, Mathieu Pellerin wrote:
>
> Hmm a choice between too early and "too late", ;)
>
> While a sync with ongoing point release would be nice, Feb 23 seems really
> far down the road. I think there's an expectation we'd release sooner. At
> least, there's a lot of excitement and anticipation.
>
> M
>
> On Jan 9, 2018 20:22, "Jürgen E. Fischer"  wrote:
>
>> Hi Matthias,
>>
>> On Tue, 09. Jan 2018 at 12:31:32 +0100, Matthias Kuhn wrote:
>> > On 01/09/2018 11:21 AM, Mathieu Pellerin wrote:
>> > > > Also for the bug fixing, lets give it a full month
>> > >
>> > > If the project settled on Feb. 8, can we have an official
>> > > acknowledgement on this? Maybe a simple mail to the dev list stating
>> > > "QGIS 3.0 will be released on Feb. 8, 2018".
>>
>> > Feb 8 sounds like a sensible date to me, some time left for fixing but
>> > still in a reasonable timeframe.
>>
>> I'd opt for the next set point release dates.  19.1. is probably to
>> early, so
>> 23.2. would be up next.
>>
>> 3.0.0 would be release then. 2.14.22 would be the last release of the old
>> LTR
>> on 19.1. and would be replaced by 2.18.17 when 3.0.0 is released.
>>
>>
>> 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
>
>
> ___
> 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
___
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] Where do we sit with respect to release?

[Andreas Neumann]

Cool, excitement and anticipation is good - then they can all test PRIOR
! to the release (the nightlies and weeklies) and help make the
release better! 

We did not promise any date. We should release when we think it is in a
good shape. 

Andreas 

On 2018-01-09 14:33, Mathieu Pellerin wrote:

> Hmm a choice between too early and "too late", ;) 
> 
> While a sync with ongoing point release would be nice, Feb 23 seems really 
> far down the road. I think there's an expectation we'd release sooner. At 
> least, there's a lot of excitement and anticipation. 
> 
> M 
> 
> On Jan 9, 2018 20:22, "Jürgen E. Fischer"  wrote:
> 
>> Hi Matthias,
>> 
>> On Tue, 09. Jan 2018 at 12:31:32 +0100, Matthias Kuhn wrote:
>>> On 01/09/2018 11:21 AM, Mathieu Pellerin wrote:
> Also for the bug fixing, lets give it a full month
 
 If the project settled on Feb. 8, can we have an official
 acknowledgement on this? Maybe a simple mail to the dev list stating
 "QGIS 3.0 will be released on Feb. 8, 2018".
>> 
>>> Feb 8 sounds like a sensible date to me, some time left for fixing but
>>> still in a reasonable timeframe.
>> 
>> I'd opt for the next set point release dates.  19.1. is probably to early, so
>> 23.2. would be up next.
>> 
>> 3.0.0 would be release then. 2.14.22 would be the last release of the old LTR
>> on 19.1. and would be replaced by 2.18.17 when 3.0.0 is released.
>> 
>> 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 [1]
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer [1]
> 
> ___
> 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

 

Links:
--
[1] 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] Where do we sit with respect to release?

[Mathieu Pellerin]

Hmm a choice between too early and "too late", ;)

While a sync with ongoing point release would be nice, Feb 23 seems really
far down the road. I think there's an expectation we'd release sooner. At
least, there's a lot of excitement and anticipation.

M

On Jan 9, 2018 20:22, "Jürgen E. Fischer"  wrote:

> Hi Matthias,
>
> On Tue, 09. Jan 2018 at 12:31:32 +0100, Matthias Kuhn wrote:
> > On 01/09/2018 11:21 AM, Mathieu Pellerin wrote:
> > > > Also for the bug fixing, lets give it a full month
> > >
> > > If the project settled on Feb. 8, can we have an official
> > > acknowledgement on this? Maybe a simple mail to the dev list stating
> > > "QGIS 3.0 will be released on Feb. 8, 2018".
>
> > Feb 8 sounds like a sensible date to me, some time left for fixing but
> > still in a reasonable timeframe.
>
> I'd opt for the next set point release dates.  19.1. is probably to early,
> so
> 23.2. would be up next.
>
> 3.0.0 would be release then. 2.14.22 would be the last release of the old
> LTR
> on 19.1. and would be replaced by 2.18.17 when 3.0.0 is released.
>
>
> 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
>
___
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] Where do we sit with respect to release?

[Jürgen E . Fischer]

Hi Matthias,

On Tue, 09. Jan 2018 at 12:31:32 +0100, Matthias Kuhn wrote:
> On 01/09/2018 11:21 AM, Mathieu Pellerin wrote:
> > > Also for the bug fixing, lets give it a full month
> >
> > If the project settled on Feb. 8, can we have an official
> > acknowledgement on this? Maybe a simple mail to the dev list stating
> > "QGIS 3.0 will be released on Feb. 8, 2018".

> Feb 8 sounds like a sensible date to me, some time left for fixing but
> still in a reasonable timeframe.

I'd opt for the next set point release dates.  19.1. is probably to early, so
23.2. would be up next.

3.0.0 would be release then. 2.14.22 would be the last release of the old LTR
on 19.1. and would be replaced by 2.18.17 when 3.0.0 is released.


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] Where do we sit with respect to release?

[Matthias Kuhn]

On 01/09/2018 11:21 AM, Mathieu Pellerin wrote:
> > Also for the bug fixing, lets give it a full month
>
> If the project settled on Feb. 8, can we have an official
> acknowledgement on this? Maybe a simple mail to the dev list stating
> "QGIS 3.0 will be released on Feb. 8, 2018".

Feb 8 sounds like a sensible date to me, some time left for fixing but
still in a reasonable timeframe.

>
> Thanks,
>
> Math
>
>
> On Tue, Jan 9, 2018 at 5:18 PM, Tim Sutton  > wrote:
>
>
> I’d also like to suggest that we move to using loomio more when an
> unequivocal decision is needed on these things so that we can all
> be clear on what was decided.
>

Yep, that sounds good for taking decisions after fleshing out a/the
proposal(s) on the list first.

Regards
Matthias

>
> Regards
>
> Tim
>

___
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] Where do we sit with respect to release?

[Mathieu Pellerin]

> Also for the bug fixing, lets give it a full month

If the project settled on Feb. 8, can we have an official acknowledgement
on this? Maybe a simple mail to the dev list stating "QGIS 3.0 will be
released on Feb. 8, 2018".

Thanks,

Math


On Tue, Jan 9, 2018 at 5:18 PM, Tim Sutton  wrote:

> Hi Régis
>
> We have discussed beta versions many times through the years and consensus
> is always not to make a beta. We have nightly builds and an overloaded
> release manager, lets keep things simple and follow regular procedures as
> much as possible.
>
> We discussed this (conveying to our users that the 3.0.0 may not be the
> most stable software on the planet) last night at the PSC meeting and our
> recommendation is that we will tweak the splash to include a message that
> this is an early version with a lot of big changes, use only after testing
> (Anita will come up with better wording). In a subsequent bug fix release
> (e.g. 3.0.x) we can remove that message from the splash. We felt this was
> the highest visibility way to message this to our users on all platforms
> regardless of the installation mode.
>
> Also for the bug fixing, lets give it a full month - there are a lot of
> other things that need to happen - like giving plugin authors time to port
> their work now that the API is fixed, getting the release visual changelog
> written, fixing bugs, packing for Mac etc.
>
> I’d also like to suggest that we move to using loomio more when an
> unequivocal decision is needed on these things so that we can all be clear
> on what was decided.
>
> Regards
>
> Tim
>
>
> On 09 Jan 2018, at 11:37, Régis Haubourg  wrote:
>
> @Bernd, I don't want to open any can of worm :) . Reading again the
> discussion where you ask for it, I realize that no decision was taken on
> that BETA branding.
>
> @Borys, thanks for the pointer. I'll see if Paul is available to merge
> that.
>
> Régis
>
> 2018-01-09 10:03 GMT+01:00 Borys Jurgiel :
>
>> On wtorek, 9 stycznia 2018 08:55:22 CET Régis Haubourg wrote:
>> > Hi all,
>> > given the small impacts and the benefit of emptying the PR queue, can
>> we go
>> > for a merge of https://github.com/qgis/QGIS/pull/5663 (named
>> transactions
>> > in executeSQL)?
>> > I know we voted to not add it in the freeze exemptions, but that was in
>> the
>> > target of keeping a release date in end 2017. Now that time is passing,
>> and
>> > the hypothesis of a QGIS 3.0 "beta" being advertised, I think we should
>> > have it in the release.
>>
>> A small correction: we definitely voted to add it (11:2), just Paul was
>> opposed.
>>
>> https://www.loomio.org/p/EnrX0paG/-5663-add-a-name-for-trans
>> actions-created-from-executesql
>>
>> Regards,
>> Borys
>>
>
> ___
> 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*
>
> *Co-founder:* Kartoza
> *Project chair:* QGIS.org
>
> 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
>
>
> ___
> 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] Where do we sit with respect to release?

[Tim Sutton]

Hi Régis

We have discussed beta versions many times through the years and consensus is 
always not to make a beta. We have nightly builds and an overloaded release 
manager, lets keep things simple and follow regular procedures as much as 
possible.

We discussed this (conveying to our users that the 3.0.0 may not be the most 
stable software on the planet) last night at the PSC meeting and our 
recommendation is that we will tweak the splash to include a message that this 
is an early version with a lot of big changes, use only after testing (Anita 
will come up with better wording). In a subsequent bug fix release (e.g. 3.0.x) 
we can remove that message from the splash. We felt this was the highest 
visibility way to message this to our users on all platforms regardless of the 
installation mode.

Also for the bug fixing, lets give it a full month - there are a lot of other 
things that need to happen - like giving plugin authors time to port their work 
now that the API is fixed, getting the release visual changelog written, fixing 
bugs, packing for Mac etc.

I’d also like to suggest that we move to using loomio more when an unequivocal 
decision is needed on these things so that we can all be clear on what was 
decided.

Regards

Tim


> On 09 Jan 2018, at 11:37, Régis Haubourg  wrote:
> 
> @Bernd, I don't want to open any can of worm :) . Reading again the 
> discussion where you ask for it, I realize that no decision was taken on that 
> BETA branding. 
> 
> @Borys, thanks for the pointer. I'll see if Paul is available to merge that. 
> 
> Régis
> 
> 2018-01-09 10:03 GMT+01:00 Borys Jurgiel  >:
> On wtorek, 9 stycznia 2018 08:55:22 CET Régis Haubourg wrote:
> > Hi all,
> > given the small impacts and the benefit of emptying the PR queue, can we go
> > for a merge of https://github.com/qgis/QGIS/pull/5663 
> >  (named transactions
> > in executeSQL)?
> > I know we voted to not add it in the freeze exemptions, but that was in the
> > target of keeping a release date in end 2017. Now that time is passing, and
> > the hypothesis of a QGIS 3.0 "beta" being advertised, I think we should
> > have it in the release.
> 
> A small correction: we definitely voted to add it (11:2), just Paul was 
> opposed.
> 
> https://www.loomio.org/p/EnrX0paG/-5663-add-a-name-for-transactions-created-from-executesql
>  
> 
> 
> Regards,
> Borys
> 
> ___
> 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

Co-founder: Kartoza
Project chair: QGIS.org

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

___
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] Where do we sit with respect to release?

[Mathieu Pellerin]

I'm a big -1 for this "beta" idea, and I really don't think we should aim
at any date beyond Feb 8.

Andreas, yep, we still need to fix some issues but none that can't be
addressed during the two (three? :'( ;) ) week of hard freeze. As for the
auth manager error, a fix has just been submitted:
https://github.com/qgis/QGIS/pull/6020

Cheers

On Tue, Jan 9, 2018 at 1:59 PM, Andreas Neumann  wrote:

> Hi,
>
> I would prefer Feb 8 over Jan 31. Still quite a few unsolved issues. It
> would be nice to have packages ready before the dev meeting in Funchal
> (second half of February).
>
> As an example I still get error messages about the authentication manager
> not able to open password files or reading/storing information about
> passwords. Seems pretty serious to me - we should not ship in such a state.
>
> Andreas
>
>
>
> On 2018-01-09 01:22, Mathieu Pellerin wrote:
>
> Let that person with authority also lock in the release date.
>
> Very last day of this month, Jan 31? While Feb 8 isn't that far, it'd
> still be great to deliver our product by the end of this month. Either way
> we need to settle on a date.
>
> M
>
> On Jan 9, 2018 05:27, "Nyall Dawson"  wrote:
>
>> On 7 January 2018 at 21:55, Tim Sutton  wrote:
>>
>> > Yes - the voting is closed on all and they all passed.
>> >
>> > - after the voting period expires we enter hard freeze regardless
>> >
>> >
>>
>> Given that those 3 PRs are merged now, I think we can enter hard
>> freeze safely. Woohoo!
>>
>> Does someone with authority want to lock this in and officially announce?
>>
>> Nyall
>> ___
>> 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
>
>
>
___
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] Where do we sit with respect to release?

[Borys Jurgiel]

On wtorek, 9 stycznia 2018 08:55:22 CET Régis Haubourg wrote:
> Hi all,
> given the small impacts and the benefit of emptying the PR queue, can we go
> for a merge of https://github.com/qgis/QGIS/pull/5663 (named transactions
> in executeSQL)?
> I know we voted to not add it in the freeze exemptions, but that was in the
> target of keeping a release date in end 2017. Now that time is passing, and
> the hypothesis of a QGIS 3.0 "beta" being advertised, I think we should
> have it in the release.

A small correction: we definitely voted to add it (11:2), just Paul was opposed.

https://www.loomio.org/p/EnrX0paG/-5663-add-a-name-for-transactions-created-from-executesql

Regards,
Borys
___
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] Where do we sit with respect to release?

[Régis Haubourg]

@Bernd, I don't want to open any can of worm :) . Reading again the
discussion where you ask for it, I realize that no decision was taken on
that BETA branding.

@Borys, thanks for the pointer. I'll see if Paul is available to merge
that.

Régis

2018-01-09 10:03 GMT+01:00 Borys Jurgiel :

> On wtorek, 9 stycznia 2018 08:55:22 CET Régis Haubourg wrote:
> > Hi all,
> > given the small impacts and the benefit of emptying the PR queue, can we
> go
> > for a merge of https://github.com/qgis/QGIS/pull/5663 (named
> transactions
> > in executeSQL)?
> > I know we voted to not add it in the freeze exemptions, but that was in
> the
> > target of keeping a release date in end 2017. Now that time is passing,
> and
> > the hypothesis of a QGIS 3.0 "beta" being advertised, I think we should
> > have it in the release.
>
> A small correction: we definitely voted to add it (11:2), just Paul was
> opposed.
>
> https://www.loomio.org/p/EnrX0paG/-5663-add-a-name-for-
> transactions-created-from-executesql
>
> Regards,
> Borys
>
___
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] Where do we sit with respect to release?

[Régis Haubourg]

Hi all,
given the small impacts and the benefit of emptying the PR queue, can we go
for a merge of https://github.com/qgis/QGIS/pull/5663 (named transactions
in executeSQL)?
I know we voted to not add it in the freeze exemptions, but that was in the
target of keeping a release date in end 2017. Now that time is passing, and
the hypothesis of a QGIS 3.0 "beta" being advertised, I think we should
have it in the release.
Any objection if I ask Paul to merge that?
Cheers
Régis

2018-01-09 7:59 GMT+01:00 Andreas Neumann :

> Hi,
>
> I would prefer Feb 8 over Jan 31. Still quite a few unsolved issues. It
> would be nice to have packages ready before the dev meeting in Funchal
> (second half of February).
>
> As an example I still get error messages about the authentication manager
> not able to open password files or reading/storing information about
> passwords. Seems pretty serious to me - we should not ship in such a state.
>
> Andreas
>
>
>
> On 2018-01-09 01:22, Mathieu Pellerin wrote:
>
> Let that person with authority also lock in the release date.
>
> Very last day of this month, Jan 31? While Feb 8 isn't that far, it'd
> still be great to deliver our product by the end of this month. Either way
> we need to settle on a date.
>
> M
>
> On Jan 9, 2018 05:27, "Nyall Dawson"  wrote:
>
>> On 7 January 2018 at 21:55, Tim Sutton  wrote:
>>
>> > Yes - the voting is closed on all and they all passed.
>> >
>> > - after the voting period expires we enter hard freeze regardless
>> >
>> >
>>
>> Given that those 3 PRs are merged now, I think we can enter hard
>> freeze safely. Woohoo!
>>
>> Does someone with authority want to lock this in and officially announce?
>>
>> Nyall
>> ___
>> 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
>
>
>
> ___
> 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] Where do we sit with respect to release?

[Andreas Neumann]

Hi, 

I would prefer Feb 8 over Jan 31. Still quite a few unsolved issues. It
would be nice to have packages ready before the dev meeting in Funchal
(second half of February). 

As an example I still get error messages about the authentication
manager not able to open password files or reading/storing information
about passwords. Seems pretty serious to me - we should not ship in such
a state. 

Andreas 

On 2018-01-09 01:22, Mathieu Pellerin wrote:

> Let that person with authority also lock in the release date.  
> 
> Very last day of this month, Jan 31? While Feb 8 isn't that far, it'd still 
> be great to deliver our product by the end of this month. Either way we need 
> to settle on a date. 
> 
> M 
> 
> On Jan 9, 2018 05:27, "Nyall Dawson"  wrote:
> 
>> On 7 January 2018 at 21:55, Tim Sutton  wrote:
>> 
>>> Yes - the voting is closed on all and they all passed.
>>> 
>>> - after the voting period expires we enter hard freeze regardless
>>> 
>>> 
>> 
>> Given that those 3 PRs are merged now, I think we can enter hard
>> freeze safely. Woohoo!
>> 
>> Does someone with authority want to lock this in and officially announce?
>> 
>> Nyall
>> ___
>> QGIS-Developer mailing list
>> QGIS-Developer@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer [1]
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer [1]
> 
> ___
> 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

 

Links:
--
[1] 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] Where do we sit with respect to release?

[Mathieu Pellerin]

Let that person with authority also lock in the release date.

Very last day of this month, Jan 31? While Feb 8 isn't that far, it'd still
be great to deliver our product by the end of this month. Either way we
need to settle on a date.

M

On Jan 9, 2018 05:27, "Nyall Dawson"  wrote:

> On 7 January 2018 at 21:55, Tim Sutton  wrote:
>
> > Yes - the voting is closed on all and they all passed.
> >
> > - after the voting period expires we enter hard freeze regardless
> >
> >
>
> Given that those 3 PRs are merged now, I think we can enter hard
> freeze safely. Woohoo!
>
> Does someone with authority want to lock this in and officially announce?
>
> Nyall
> ___
> 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] Where do we sit with respect to release?

[Nyall Dawson]

On 7 January 2018 at 21:55, Tim Sutton  wrote:

> Yes - the voting is closed on all and they all passed.
>
> - after the voting period expires we enter hard freeze regardless
>
>

Given that those 3 PRs are merged now, I think we can enter hard
freeze safely. Woohoo!

Does someone with authority want to lock this in and officially announce?

Nyall
___
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] Where do we sit with respect to release?

[Paolo Cavallini]

+1

Il 7 gennaio 2018 19:52:29 CET, Tim Sutton  ha scritto:
>Hi
>
>> On 07 Jan 2018, at 13:17, Andreas Neumann 
>wrote:
>> 
>> Hi,
>> 
>> I would also prefer:
>> 
>> to go into freeze soon
>> if possible merge the 3 PRs that were recently voted on for
>duplicating features
>> have 1 month of bug fixing - 2 weeks seems to short for me.
>> Note that we already had a couple of weeks bug fixing from some core
>devs in parallel with the soft freeze, but as this is a major release
>with so many changes I would prefer 1 month after the hard freeze.
>> 
>> 
>
>+1 for 1 month from me - that would peg the release date as something
>like 8 Feb then….
>
>Regards
>
>Tim
>
>> Andreas
>> 
>> On 07.01.2018 12:09, Denis Rouzaud wrote:
>>> 
>>> 
>>> Le sam. 6 janv. 2018 à 22:27, Nyall Dawson > a écrit :
>>> Hi all,
>>> 
>>> Just for clarification, is this a correct summary of the freeze
>situation?
>>> - hard freeze is coming
>>> - those 3 PRs may be merged, if the voting for each passes
>>> - after the voting period expires we enter hard freeze regardless
>>> 
>>> I had that in mind too
>>> 
>>> And following hard freeze, did we agree to a month of bug fixing
>>> before release? Or 2 weeks?
>>> 
>>> I thought it was 1 month but I can't recall a decision. I would vote
>for a month. 
>>> 
>>> Denis 
>>> 
>>> 
>>> ___
>>> 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
>
>—
>
>
>
>
>
>
>
>Tim Sutton
>
>Co-founder: Kartoza
>Project chair: QGIS.org
>
>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

-- 
Inviato dal mio dispositivo Android con K-9 Mail. Perdonate la brevità.___
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] Where do we sit with respect to release?

[Tim Sutton]

Hi

> On 07 Jan 2018, at 13:17, Andreas Neumann  wrote:
> 
> Hi,
> 
> I would also prefer:
> 
> to go into freeze soon
> if possible merge the 3 PRs that were recently voted on for duplicating 
> features
> have 1 month of bug fixing - 2 weeks seems to short for me.
> Note that we already had a couple of weeks bug fixing from some core devs in 
> parallel with the soft freeze, but as this is a major release with so many 
> changes I would prefer 1 month after the hard freeze.
> 
> 

+1 for 1 month from me - that would peg the release date as something like 8 
Feb then….

Regards

Tim

> Andreas
> 
> On 07.01.2018 12:09, Denis Rouzaud wrote:
>> 
>> 
>> Le sam. 6 janv. 2018 à 22:27, Nyall Dawson > > a écrit :
>> Hi all,
>> 
>> Just for clarification, is this a correct summary of the freeze situation?
>> - hard freeze is coming
>> - those 3 PRs may be merged, if the voting for each passes
>> - after the voting period expires we enter hard freeze regardless
>> 
>> I had that in mind too
>> 
>> And following hard freeze, did we agree to a month of bug fixing
>> before release? Or 2 weeks?
>> 
>> I thought it was 1 month but I can't recall a decision. I would vote for a 
>> month. 
>> 
>> Denis 
>> 
>> 
>> ___
>> 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

—







Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

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

___
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] Where do we sit with respect to release?

[Tim Sutton]

Hi


> On 07 Jan 2018, at 04:27, Nyall Dawson  wrote:
> 
> Hi all,
> 
> Just looking for some clarification re freeze/release.
> 
> My understanding is that the last loomio "extend freeze" vote was
> blocked, and that all the freeze exempted PRs are now merged (I
> consider https://github.com/qgis/QGIS/pull/5913 is a bug fix, not a
> feature).

Yes blocked.

> 
> This would hint that me that we are now in hard freeze, but I'm not
> sure how that relates to the voting occuring in
> https://www.loomio.org/d/38Aiya0q/3-0-soft-freeze-exemptions?utm_campaign=missed_yesterday&utm_medium=email&utm_source=user_mailer
> to grant exemptions to 3 more PRs.

If these PR’s are all ready we should just merge them straight away. If there 
is pending work still I think they should hold over till 3.2

> 
> Just for clarification, is this a correct summary of the freeze situation?
> - hard freeze is coming

Yes my understanding was that is is now in effect (assuming those 3 get merged 
today) and that only bug fixes should happen now.

> - those 3 PRs may be merged, if the voting for each passes

Yes - the voting is closed on all and they all passed.

> - after the voting period expires we enter hard freeze regardless

Yes

> 
> And following hard freeze, did we agree to a month of bug fixing
> before release? Or 2 weeks?

I had proposed that we do bug fixing until end Jan 2018. I think there was 
general agreement to that time frame although we did not make a formal vote.

Regards

Tim

> 
> Nyall
> ___
> 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

Co-founder: Kartoza
Project chair: QGIS.org

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

___
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] Where do we sit with respect to release?

[Andreas Neumann]

Hi,

I would also prefer:

1. to go into freeze soon
2. if possible merge the 3 PRs that were recently voted on for
   duplicating features
3. have 1 month of bug fixing - 2 weeks seems to short for me.

Note that we already had a couple of weeks bug fixing from some core 
devs in parallel with the soft freeze, but as this is a major release 
with so many changes I would prefer 1 month after the hard freeze.


Andreas


On 07.01.2018 12:09, Denis Rouzaud wrote:



Le sam. 6 janv. 2018 à 22:27, Nyall Dawson > a écrit :


Hi all,

Just for clarification, is this a correct summary of the freeze
situation?
- hard freeze is coming
- those 3 PRs may be merged, if the voting for each passes
- after the voting period expires we enter hard freeze regardless


I had that in mind too


And following hard freeze, did we agree to a month of bug fixing
before release? Or 2 weeks?


I thought it was 1 month but I can't recall a decision. I would vote 
for a month.


Denis


___
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] Where do we sit with respect to release?

[Denis Rouzaud]

Le sam. 6 janv. 2018 à 22:27, Nyall Dawson  a
écrit :

> Hi all,
>
> Just for clarification, is this a correct summary of the freeze situation?
> - hard freeze is coming
> - those 3 PRs may be merged, if the voting for each passes
> - after the voting period expires we enter hard freeze regardless
>

I had that in mind too

>
> And following hard freeze, did we agree to a month of bug fixing
> before release? Or 2 weeks?
>

I thought it was 1 month but I can't recall a decision. I would vote for a
month.

Denis
___
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] Where do we sit with respect to release?

[Paolo Cavallini]

Hi all,

Il 07/01/2018 03:27, Nyall Dawson ha scritto:

> Just for clarification, is this a correct summary of the freeze situation?
> - hard freeze is coming
> - those 3 PRs may be merged, if the voting for each passes
> - after the voting period expires we enter hard freeze regardless
> 
> And following hard freeze, did we agree to a month of bug fixing
> before release?

This is what I understood.
All the best.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis
___
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