Hi Idan,
On Sun, 02. Apr 2017 at 13:55:08 +0300, Idan Miara wrote:
> Shouldn't it say PR in the following line?
> LTR 2.18.7 2.14.15 19.05.2017 20 4
No, starting with 2.18.7 2.18 will be tagged LTR. Not changing much otherwise
as 2.18 will continue to be the LR.
Jürgen
--
Jürgen E. Fischer
Hi,
Yes, good catch. Fixed in
https://github.com/qgis/QGIS-Website/commit/e38b8c09d51f6ba4d082fb4063f9b33ab7cbf874
Thanks Idan,
Harrissou
2017-04-02 12:55 GMT+02:00 Idan Miara :
> Hi,
>
> Shouldn't it say PR in the following line?
> LTR 2.18.7 2.14.15 19.05.2017 20 4
>
> On 1
Hi,
Shouldn't it say PR in the following line?
LTR 2.18.7 2.14.15 19.05.2017 20 4
On 1 April 2017 at 12:11, Jürgen E. Fischer wrote:
> Hi Harrissou,
>
> On Fri, 31. Mar 2017 at 21:53:33 +0200, DelazJ wrote:
> > #. 3.0 will be a LTR (actually from 3.0.9 - nine months after first
Hi Jürgen,
Thanks for the fix and explanation.
Regards,
Harrissou
Le samedi 1 avril 2017, Jürgen E. Fischer a écrit :
> Hi Harrissou,
>
> On Fri, 31. Mar 2017 at 21:53:33 +0200, DelazJ wrote:
>> #. 3.0 will be a LTR (actually from 3.0.9 - nine months after first
>> release?)
>
>
Hi,
I came across reading QGIS release schedule at
http://qgis.org/en/site/getinvolved/development/roadmap.
html#release-schedule and wonder if that really reflects the decision that
was taken. The online roadmap exposed that:
#. 3.0 will be a LTR (actually from 3.0.9 - nine months after first
Matthias Kuhn wrote:
> I think having 2.18.x and 3.2.x available in parallel for an extended
> period is a good thing (...) but with a clear deadline for 2.18 so we are
> not stuck in the 2 release series forever.
and Jürgen E. Fischer wrote:
> When a new LTR is released we have a period where
Hi Harrissou,
On Wed, 22. Feb 2017 at 15:22:11 +0100, DelazJ wrote:
> I think there usually (ok! it happens only once) is an overlap between two
> LT releases: 2.8 was maintained few months after 2.14 (I think it was
> stopped when 2.16 was released).
Yes.
We build for two package repositories.
Personally I would like to see a 3.x release become LTR as soon as
possible. 3.0 should be skipped because despite it's incredibly high
stability there could potentially still be problems. So the next in line
is 3.2.
I think having 2.18.x and 3.2.x available in parallel for an extended
period is
It's an option, too. The question is which one is supposed to be more mature,
stable and polished: 3.2.5 or 3.4.0. Anyway, in both cases the lifetime of
2.18 LTR seems to be clear now.
Dnia środa, 22 lutego 2017 15:22:11 DelazJ pisze:
> Hi,
>
> I think there usually (ok! it happens only once)
Hi,
I think there usually (ok! it happens only once) is an overlap between two
LT releases: 2.8 was maintained few months after 2.14 (I think it was
stopped when 2.16 was released) -
http://qgis.org/en/site/getinvolved/development/roadmap.html
So following that logic, 3.2 would be released in
Dnia środa, 22 lutego 2017 14:45:07 Borys Jurgiel pisze:
> Other options would be: retire 2.18 LTR in January 2018 or postpone 3.2
> until June 2018. Both look unacceptable for me.
I mean to* me of course - they look to me, not 'unacceptable for me'. I'm
sorry :)
Regards,
Borys
Tim Sutton said:
> Personally I was hoping for 2.18 LTR to last from June 2017 to June 2018
> and then releasing 3.2 In June 2018.
>
> * retire 2.14 in June 2017
> * 2.18 becomes LTR from June 2017 to ***June*** 2018
> * 3.0 feature freeze in July 2017
> * release 3.0 in Sept 2017
> * release
Hi
On Tue, Feb 21, 2017 at 6:38 PM, Borys Jurgiel
wrote:
> Hi,
>
> Dnia wtorek, 21 lutego 2017 14:49:14 Tim Sutton pisze:
> > Just to confirm what Paolo said, the issue was raised by Paolo at our
> PSC
> > meeting 2 months ago (all meeting minutes are publicly available
Hi,
Dnia wtorek, 21 lutego 2017 14:49:14 Tim Sutton pisze:
> Just to confirm what Paolo said, the issue was raised by Paolo at our PSC
> meeting 2 months ago (all meeting minutes are publicly available at
> https://github.com/qgis/qgis/wiki#psc-meeting-minutes)
Unfortunately the last meeting is
Hi
On Tue, Feb 21, 2017 at 10:25 AM, Vincent Picavet (ml) <
vincent...@oslandia.com> wrote:
> Hi Paolo,
>
> Please excuse me if I missed something, but I am quite surprised, not by
> the decisions themselves, but the process of these decisions.
>
> I have seen no call for meeting, no message to
Il 21/02/2017 09:25, Vincent Picavet (ml) ha scritto:
> The topic is really important and has deep consequences for all of our
> users, funders, developers. The least we can do is ask them for their
> advice and feedback.
Hi Vincent,
we had a quick meeting among people who is doing most of the
Hi Paolo,
Please excuse me if I missed something, but I am quite surprised, not by
the decisions themselves, but the process of these decisions.
I have seen no call for meeting, no message to the list to gather
advices, no mention to voting members neither of this IRC meeting happening.
The
Hi,
Il 20/02/2017 11:59, DelazJ ha scritto:
> * retire 2.14 in June 2017
> * 2.18 becomes LTR from June 2017 to 2018
> * 3.0 feature freeze in July 2017
> * release 3.0 in Sept 2017
> * release 3.2 as next LTR in release 3.0 + 4 Months (eta June 2018).
>
> You mean 3.2
Hi Paolo (and all)
2017-02-20 11:17 GMT+01:00 Paolo Cavallini :
> Hi all,
> during a fast and productive IRC meeting today we have come out with a
> proposal for the management of current and future versions of QGIS:
>
> Thanks to you
> * retire 2.14 in June 2017
> *
19 matches
Mail list logo