Great, thanks!
Il 28/04/20 02:06, Nyall Dawson ha scritto:
> On Mon, 27 Apr 2020 at 21:55, Jürgen E. Fischer wrote:
>>
>> Hi Paolo,
>>
>> On Mon, 27. Apr 2020 at 09:08:01 +0200, Paolo Cavallini wrote:
>>> Good idea indeed.
>>> I'd leave the implementation to the Release Manager, but I think a
>>>
On Mon, 27 Apr 2020 at 21:55, Jürgen E. Fischer wrote:
>
> Hi Paolo,
>
> On Mon, 27. Apr 2020 at 09:08:01 +0200, Paolo Cavallini wrote:
> > Good idea indeed.
> > I'd leave the implementation to the Release Manager, but I think a
> > simple and good option would be:
> > https://nextcloud.osgeo.org/
Hi Jurgen,
thank you for your fast reply and change. Amazing.
I did tests integration in MS Outlook, Gmail Calendar and Thunderbird and
works like a charm so I guess this can work well for the rest apps.
@Nathan you are thinking about the plot roadmap and table schedule in the
sphinx side where
Hi Paolo,
On Mon, 27. Apr 2020 at 09:08:01 +0200, Paolo Cavallini wrote:
> Good idea indeed.
> I'd leave the implementation to the Release Manager, but I think a
> simple and good option would be:
> https://nextcloud.osgeo.org/apps/calendar/
> In fact, all Osgeo projects could add their schedule h
Ola João
Il 27/04/20 12:02, João Gaspar ha scritto:
> If I not wrong the open standard calendar is .ics
> (https://icalendar.org/) so I guess It useful to have this format to be
> interoperable with everyone and create a way to share this data in a
> graphic plot and/or table as Nathan suggests.
Hi again,
I did a little search and the QGIS Roadmap from the QGIS website is based
on Google Sheets that is updated and then upload to the website through
python scripting. We can use this Google sheets and try to sync as calendar
events
I've check this if we use the Google Sheets approach:
htt
This is a great idea.
+1 to use OSGeo nextcloud
Angelos
On 4/27/20 10:08 AM, Paolo Cavallini wrote:
Good idea indeed.
I'd leave the implementation to the Release Manager, but I think a
simple and good option would be:
https://nextcloud.osgeo.org/apps/calendar/
In fact, all Osgeo projects could a
Good idea indeed.
I'd leave the implementation to the Release Manager, but I think a
simple and good option would be:
https://nextcloud.osgeo.org/apps/calendar/
In fact, all Osgeo projects could add their schedule here.
I'm available for help if necessary.
Cheers.
Il 27/04/20 07:59, Nathan Woodrow
Yes, please! That would be super handy.
I have also though about a display like this
[image: image.png]
On Mon, Apr 27, 2020 at 1:41 PM Nyall Dawson wrote:
> On Sun, 26 Apr 2020 at 06:27, João Gaspar
> wrote:
> >
> > Hi devs,
> > it is possible or integrate the roadmap of releases in a share
On Sun, 26 Apr 2020 at 06:27, João Gaspar wrote:
>
> Hi devs,
> it is possible or integrate the roadmap of releases in a shared calendar?
>
> The idea is to receive in the Calendar the releases dates through calendar
> notifications to easily manager test and deploy QGIS releases
>
> I don't know
Hi devs,
it is possible or integrate the roadmap of releases in a shared calendar?
The idea is to receive in the Calendar the releases dates through calendar
notifications to easily manager test and deploy QGIS releases
I don't know if this make sense please let me know if I need to clarify
more
Hi Martin,
On Tue, 26. Nov 2013 at 17:29:15 +0700, Martin Dobias wrote:
> Following the previous thread [1] about the roadmap, can we set up a
> preliminary roadmap for the next release? It seems that Jürgen's suggestion
> to do time-based releases every 4 months was widely accepted, with the comb
Hi all (and especially Jürgen)
Following the previous thread [1] about the roadmap, can we set up a
preliminary roadmap for the next release? It seems that Jürgen's
suggestion to do time-based releases every 4 months was widely
accepted, with the combo Feb/Jun/Oct being most popular. So... what
ab
On 05-11-13 11:23, Jürgen E. Fischer wrote:
> Does jan/may/sep sound preferable? feb/jun/oct or mar/jul/nov or apr/aug/dec
> any better? Any preference on the week or weekday such a release should
> happen
> (eg. 3rd friday of the month)?
Good plan! I do not care which three months, it will alw
I d try to avoid august and December due to many people having holidays.
jan/may/sep would coincide with the hack fest which might be sub optimal.
+1 for feb/jun/oct or mar/jul/nov
if we consider the hack fest in sept/april, then the feb schedule would
have the hackfest in the feature freeze mon
+1 to feb/jun/oct for me.
- Nathan
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer
Hi,
On Tue, 05. Nov 2013 at 13:37:12 +0100, Vincent Picavet wrote:
> > Does jan/may/sep sound preferable? feb/jun/oct or mar/jul/nov or
> > apr/aug/dec any better? Any preference on the week or weekday such a
> > release should happen (eg. 3rd friday of the month)?
> Better not have a release
Le mardi 5 novembre 2013 11:23:11, Jürgen E. Fischer a écrit :
> Anyway, the 4 months would be split into three months of development and
> one month for testing, bugfixing, translating and release preparations in
> a freeze period.
Great to have a fixed time release plan ! Definite +1 for that !
+1 from me for this kind of release schedule. Knowing that there is a
release coming in X months puts users minds at ease and lets devs focus on
what they can do and when, and not rushing things last minute.
Waiting for features is just asking for the "we will just wait for this,
and that, and th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/11/2013 12:24, Alexander Bruy ha scritto:
> I agree with Jürgen and Marco, fixed release schedule is better
> than waiting for features. Also having month for testing should be
> enough for finding most major bugs/regressions, so releases will b
Hi,
I agree with Jürgen and Marco, fixed release schedule is better than
waiting for features. Also having month for testing should be enough
for finding most major bugs/regressions, so releases will be more
stable and robust.
2013/11/5 Jürgen E. :
> Hi Paolo,
>
> On Mon, 04. Nov 2013 at 20:01:0
Hi Jürgen
Sounds good to have a fixed release schedule instead of waiting for
features ( that might eventually come ).
Things are more predictable with a fixed schedule. Additionally, with
releases every four months, it's not too bad if a feature needs to wait
until next release.
Regards,
Ma
Hi Paolo,
On Mon, 04. Nov 2013 at 20:01:02 +0100, Paolo Cavallini wrote:
> wouldn't it a good time to do it now then? :)
My/The plan is to have a fixed release every four months.
So if we started with the last release the next release would be in january,
then may and september and so forth.
Wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/11/2013 10:35, Andreas Neumann ha scritto:
> Hi,
> Am 2013-11-05 10:29, schrieb Vincent Picavet:
>> +1 Release soon, release often.
+1
what is our brand new Release Manager say about this?
All the best.
- --
Paolo Cavallini - Faunalia
www.fau
Hi,
It would be fine for me to have another release by Christmas/end of the
year. In that case, of course the multi-threaded work should be done in
2.3
However, we should not postpone the multi-threaded work further. It is
core stuff and has a lot of implications. The longer we wait, the mor
Hello,
Le mardi 5 novembre 2013 01:24:55, Nathan Woodrow a écrit :
> It would be cool if we could do a Christmas release for 2.2 and then we can
> look at things like multithreading for the next one. I don't think trying
> to rush in something like multithreading is a good idea as there is a bit
>
> expression based {categorized, graduated} symbology,
Which just need some fixing but seem to be working fine.
It would be cool if we could do a Christmas release for 2.2 and then we can
look at things like multithreading for the next one. I don't think trying
to rush in something like multi
As others have pointed out, there's already a substantial amount of new
features in qgis master. Beyond what was mentioned above, there's: world
file on qgis composer export, expression based {categorized, graduated}
symbology, notable improvements in the spatialite & postegresql drivers,
improveme
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Marco Hugentobler is working on DXF export and there are also label
speed improvements in the pipeline that did not make it into 2.0
Nyall is working on improving the print composer to behave better like
a DTP/graphic application, including bette
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I would like to see multi-threaded rendering in QGIS 2.2. Martin
Dobias could work on it. QGIS-CH could sponsor parts of it - but we
would need additional sponsors.
See these emails:
http://lists.osgeo.org/pipermail/qgis-developer/2013-Octobe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 04/11/2013 19:51, Jrgen E. Fischer ha scritto:
> Not yet - at least as far as I know.
wouldn't it a good time to do it now then? :)
thanks.
- --
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
Nuovi corsi QG
Hi Paolo,
On Mon, 04. Nov 2013 at 19:16:21 +0100, Paolo Cavallini wrote:
> Do we have a definite plan for QGIS 2.2 release?
Not yet - at least as far as I know.
Jürgen
--
Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all.
Do we have a definite plan for QGIS 2.2 release?
Thanks.
- --
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
-BEGIN PGP SIGNATURE-
Ver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 23/08/2013 18:01, Paolo Cavallini ha scritto:
> Right, these should be migrated now.
I suppose there must be an easy way to move them from one project (sextante) to
another (qgis desktop), right?
Anyone knowledgeable with redmine?
Thanks.
- --
Pa
Given the short amount of available time, I'd like to single out this bug:
http://hub.qgis.org/issues/6299
which causes the outputs to have a different encoding from the input. This
can potentially mess up analysis conducted with .shp with non-ascii
characters.
I believe Victor Olaya wont be abl
Filipe Dias ha scritto:
>Hi, and these from Sextante too:
>http://hub.qgis.org/projects/sextante/issues
>
>
>On Fri, Aug 23, 2013 at 4:42 PM, Paolo Cavallini
>wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hi all.
>> While searching for the announcement of the roadmap to 2.0 re
Hi, and these from Sextante too:
http://hub.qgis.org/projects/sextante/issues
On Fri, Aug 23, 2013 at 4:42 PM, Paolo Cavallini wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all.
> While searching for the announcement of the roadmap to 2.0 release, I
> noticed that we
> have a n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all.
While searching for the announcement of the roadmap to 2.0 release, I noticed
that we
have a number of annouuncements, wiki pages, etc, scattered over the net.
It would be better to update or remove most of them, and point to a single
documen
Hi all,
many thanks to your efforts to let us know what happened in Valmeria.
Did you had any discussion on 2.1 Roadmap?
I submitted previously my personnal wishes here [0], do you have any
feedback to give on that?
Many thanks, ( this will be my basis for next fundings, and priority will
certa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/04/2013 17:26, Régis Haubourg ha scritto:
> Sure. DB Manager as a very nice SQL editor window with
> autocompletion. Qspatialite embed the SQL Window with a user
> interface close to Mapinfo SQL window, allowing to add table names,
> column name
Paolo Cavallini wrote
> Hi Régis,
> could you please explain this?
> Improve DB manager with a SQL query assistant similar to Qspatialite one.
> All the best.
> - --
> Paolo Cavallini - Faunalia
Sure. DB Manager as a very nice SQL editor window with autocompletion.
Qspatialite embed the SQL Windo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 05/04/2013 16:27, Régis Haubourg ha scritto:
> Hi dev's and contributors. In preparation of the next Hackfest, in
> which I won't be able to join you, I would like to share my
> personnal priorities for new features and consolidation of QGIS
> 2.0.
Hi dev's and contributors.
In preparation of the next Hackfest, in which I won't be able to join you, I
would like to share my personnal priorities for new features and
consolidation of QGIS 2.0.
Sorry for doing it now, when everybody is full time on 2.0 release, but I
think next hackfest is the
Hi Borys
On Sun, Sep 19, 2010 at 10:29 PM, Borys Jurgiel wrote:
> Dnia niedziela 19 września 2010 o 18:02:20 Paolo Cavallini napisał(a):
>> Hi all.
>> Our roadmap looks outdated:
>> https://trac.osgeo.org/qgis/roadmap
>> 1.6 should be due in 10 days, which is unrealistic.
>> I would suggest to po
Dnia niedziela 19 września 2010 o 18:02:20 Paolo Cavallini napisał(a):
> Hi all.
> Our roadmap looks outdated:
> https://trac.osgeo.org/qgis/roadmap
> 1.6 should be due in 10 days, which is unrealistic.
> I would suggest to postpone 1.6 to after the hackfest (let's say, 30 Nov),
I'd rather say Dec
Hi all.
Our roadmap looks outdated:
https://trac.osgeo.org/qgis/roadmap
1.6 should be due in 10 days, which is unrealistic.
I would suggest to postpone 1.6 to after the hackfest (let's say, 30 Nov),
and 2.0 to 30 April.
Of course that's not terribly important, but is a bit of cosmetics that can
ma
46 matches
Mail list logo
