+1 for the point release. And one release a month as scheduled seems
reasonable to me. But since every user can not download and install each
release, it'll be worth listing the bugs that are fixed. So the user can
clearly evaluate if it's worth updating QGIS according to his needs.
2015-11-25
ok, I can remove pull request regarding FTool message
wonderful team work... we can summarize some "lesson learned" from this bug?
cheers
Luigi Pirelli
**
* Boundless QGIS Support/Development:
On 26 November 2015 at 07:51, Luigi Pirelli wrote:
> ok, I can remove pull request regarding FTool message
>
> wonderful team work... we can summarize some "lesson learned" from this bug?
Write unit tests for critical stuff like this? Don't accept a
replacement for ftools which
Hi Jürgen
> On 25 Nov 2015, at 13:07, Jürgen E. Fischer wrote:
>
> Hi,
>
> I updated the release schedule to include dates for the point release[0]. I
> think it's easier to have fixes dates there too - instead of a "some-period of
> silence" rule.
>
> The next point release
Hi,
I updated the release schedule to include dates for the point release[0]. I
think it's easier to have fixes dates there too - instead of a "some-period of
silence" rule.
The next point release for 2.8.x and 2.12.x will be on Friday.
Any objections? Nyall and I finished our backports from
Hi!
According to my tests with Intersect and Union the ftools problem is
fixed now .. so this only "leaves" 2.10 without a fix - which we
apperently don't need (people using 2.10 should upgrade to 2.12
anyway)..
Well done!
thanks
regards
Werner
On Wed, Nov 25, 2015 at 12:07 PM, Jürgen E.
Il 25/11/2015 12:28, Werner Macho ha scritto:
> According to my tests with Intersect and Union the ftools problem is
> fixed now .. so this only "leaves" 2.10 without a fix - which we
> apperently don't need (people using 2.10 should upgrade to 2.12
> anyway)..
>
> Well done!
What a relief,
Hi,
That's a good idea - to have fixed dates for point releases.
Andreas
On 25.11.2015 12:07, Jürgen E. Fischer wrote:
Hi,
I updated the release schedule to include dates for the point release[0]. I
think it's easier to have fixes dates there too - instead of a "some-period of
silence"
On Wed, Nov 25, 2015 at 12:31 PM, Paolo Cavallini
wrote:
> Il 25/11/2015 12:28, Werner Macho ha scritto:
>
> > According to my tests with Intersect and Union the ftools problem is
> > fixed now .. so this only "leaves" 2.10 without a fix - which we
> > apperently don't