Il 27/06/2014 10:43, Vincent Picavet ha scritto:
> We should definitly get more information on our user base, gather statistics
> (anonymous, or through website stats), so that we can know what really
> matters
> to our users. We should not develop software for ourselves, but for people
> who
Hi Richard,
On Fri, 27. Jun 2014 at 09:47:55 +0200, Richard Duivenvoorde wrote:
> +1 from me with the combo:
> - source release is only announced on dev list
> - when wmu is packaged, we sent a mail to user/community list, update
> website and startup the marketing machine/twitter about it etc e
Hi,
Le vendredi 27 juin 2014 09:47:55, Richard Duivenvoorde a écrit :
> On 27-06-14 08:45, Nyall Dawson wrote:
> >> Why can't we state that release is when windows + mac + ubuntu are
> >> ready?
> >
> > +1 from me.
>
> +1 from me with the combo:
Agree with this, and to Nathan's demands.
We sho
+1 from me for Richard's combo.
On 2014/06/27 09:47, Richard Duivenvoorde wrote:
On 27-06-14 08:45, Nyall Dawson wrote:
Why can't we state that release is when windows + mac + ubuntu are ready?
+1 from me.
+1 from me with the combo:
- source release is only announced on dev list
- when w
On 27-06-14 08:45, Nyall Dawson wrote:
>> Why can't we state that release is when windows + mac + ubuntu are ready?
>>
>
> +1 from me.
+1 from me with the combo:
- source release is only announced on dev list
- when wmu is packaged, we sent a mail to user/community list, update
website and sta
On Fri, Jun 27, 2014 at 04:30:44PM +1000, Nathan Woodrow wrote:
> On Fri, Jun 27, 2014 at 3:47 PM, Sandro Santilli wrote:
> It's like saying you can't say "apples are ripe!" because then people get
> > frustrated by not finding them on their supermarket shelf.
>
> This is incorrect. The "apples
Probably the keypoint of this discussion are the different point of views
on what the dev community consider the final point of a development cycle.
Some consider it the source ball and the packaging a plus. Others include
the packages themselves (in their mindset).
I don't want to open a discussi
On 27/06/2014 4:35 pm, "Denis Rouzaud" wrote:
>
>
> For me, a summarize is: save two days of waiting (on a 4+ months
schedule) so <1% users can compile while 99% get frustrated.
I suspect the actual fraction of users who compile is much much smaller
than this. Maybe 1 in a thousand at most, proba
For me, a summarize is: save two days of waiting (on a 4+ months
schedule) so <1% users can compile while 99% get frustrated.
Why can't we state that release is when windows + mac + ubuntu are ready?
Many reported users get confused.
Last time, people were asking where to find the installer.
On Fri, Jun 27, 2014 at 3:47 PM, Sandro Santilli wrote:
> Announcing source release should have a link to the source tarball.
>
> Binary releases might even not need to be announced by the qgis team,
> as serious package managers conveniently implement those announces with
> user popups and the l
On Fri, Jun 27, 2014 at 09:03:08AM +1000, Nathan Woodrow wrote:
> a "source" release is like say "yay
> release!But no you can't have it because your just a user you have to
> wait".
You don't have to wait.
You can have it now if you want.
If you decided to give up your freedom for convenien
I am aware it was a late email, I have been busy on non qgis jobs and
haven't been able to look side ways.
On Fri, Jun 27, 2014 at 2:03 AM, Paolo Cavallini
wrote:
> 1. do not change anything in the relase schedule just one day before
> 2. announcements should be clear: (a) QGIS 2.4 is out, wait
Hi All,
I agree with Denis and Nathan on the general idea, and also with Paolo on
"don't change things on day before".
From a user point of view, I can live 2.2 behaviour, since I already have
seen what "release" meant for qgis project in 2.2. But, I think 2.6 should
go to a more common definit
Il 26/06/2014 17:27, Jürgen E. Fischer ha scritto:
> Looks like announcing the (source) release on qgis-developer and announcing
> individual packages on qgis-user would solve that problem.
IMHO:
1. do not change anything in the relase schedule just one day before
2. announcements should be clea
Hi Giovanni,
On Thu, 26. Jun 2014 at 17:02:57 +0200, G. Allegri wrote:
> I agree too for announcing when packages are ready.
> Right today, during a course, I was answering a partecipant wh asked be
> about the next release. I've told him it will happen in a few days and I
> ansewered: "I hope the
On 26.06.2014 17:02, Jürgen E. Fischer wrote:
Hi Andreas,
On Thu, 26. Jun 2014 at 14:43:19 +, Andreas Neumann wrote:
I have to agree with Nathan and Denis. It would me buch better to announce a
release when the packages are ready. I remember that last time there was some
confusion and disa
Hi Andreas,
On Thu, 26. Jun 2014 at 14:43:19 +, Andreas Neumann wrote:
> I have to agree with Nathan and Denis. It would me buch better to announce a
> release when the packages are ready. I remember that last time there was some
> confusion and disappointment by users reading tweets that QGIS
I agree too for announcing when packages are ready.
Right today, during a course, I was answering a partecipant wh asked be
about the next release. I've told him it will happen in a few days and I
ansewered: "I hope they don't do as for QGIS 2.2, when we had to go back to
the website more and mroe
Hi
I have to agree with Nathan and Denis. It would me buch better to
announce a release when the packages are ready. I remember that last
time there was some confusion and disappointment by users reading tweets
that QGIS was available and then they could not install it on their
platform.
Sorry Jü
On 26.06.2014 16:07, Jürgen E. Fischer wrote:
Hi Nathan,
[Take 25]
On Thu, 26. Jun 2014 at 22:32:01 +1000, Nathan Woodrow wrote:
No. Just like with 2.2.
I think this is a real mistake and bad PR for the project. If we want to
do it like this we need to refine out release plan better to h
Hi Nathan,
[Take 25]
On Thu, 26. Jun 2014 at 22:32:01 +1000, Nathan Woodrow wrote:
> >>No. Just like with 2.2.
> I think this is a real mistake and bad PR for the project. If we want to
> do it like this we need to refine out release plan better to have things
> line up nice and smooth so peop
The close for translations pulled in is tomorrow at 11:30 UTC..
No changes in that.. As the source is released at 12:00 as 2.4..
Don't worry.. Your language updates will surely make it..
Regards
Werner
On 26 June 2014 13:34:20 Kari Salovaara wrote:
On 06/26/2014 02:22 PM, Nathan Woodrow wrot
>>No. Just like with 2.2.
I think this is a real mistake and bad PR for the project. If we want to
do it like this we need to refine out release plan better to have things
line up nice and smooth so people get what they expect. The user isn't us,
we can build from source, they can not, nor shoul
Hi Nathan,
On Thu, 26. Jun 2014 at 21:22:54 +1000, Nathan Woodrow wrote:
> 1) Are we planning on having packages ready to go before the official
> announcement?
No. Just like with 2.2.
> 2) Is the website going to be updated before/just after the announcement to
>point to the packages?
Whe
On 06/26/2014 02:22 PM, Nathan Woodrow wrote:
Hi,
With the impending release in the next day or so I would just like to
clarify what the current plan is.
1) Are we planning on having packages ready to go before the official
announcement?
It would be quite unfair for us, translators, as we
Hi,
With the impending release in the next day or so I would just like to
clarify what the current plan is.
1) Are we planning on having packages ready to go before the official
announcement?
Personally I don't think it looks good to have nothing ready for download
as soon as the email goes ou
Hi all.
Tim, could you please update us on the plans for 2.0 release? We are ready to
help if
necessary.
All the best.
--
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
Nuovi corsi QGIS e PostGIS: http://www.faunalia.it/calendario
___
Hi
On Wed, Aug 24, 2011 at 1:57 PM, wrote:
> qgis-developer-boun...@lists.osgeo.org scritti il 23/08/2011 21.19.36
>
>> Hi All
>
>> I would like to put out a maintenance release of the 1.7 branch at the
>> end of this month. There won't be too much activity surrounding the
>> release as the bran
qgis-developer-boun...@lists.osgeo.org scritti il 23/08/2011 21.19.36
> Hi All
> I would like to put out a maintenance release of the 1.7 branch at the
> end of this month. There won't be too much activity surrounding the
> release as the branch is in feature freeze. There may have been some
> s
Hi All
I would like to put out a maintenance release of the 1.7 branch at the
end of this month. There won't be too much activity surrounding the
release as the branch is in feature freeze. There may have been some
small string changes so it would be good if the translators could give
the branch a
Hi
On Mon, Oct 18, 2010 at 11:21 AM, Jürgen E. wrote:
> Hi people,
>
> On Sat, 16. Oct 2010 at 14:30:21 -0400, Frank Warmerdam wrote:
>> We don't have legal resources "on call" and it could get quite expensive to
>> retain legal support so we very much lean towards avoiding legal conflict.
>
> Di
Hi people,
On Sat, 16. Oct 2010 at 14:30:21 -0400, Frank Warmerdam wrote:
> We don't have legal resources "on call" and it could get quite expensive to
> retain legal support so we very much lean towards avoiding legal conflict.
Did anyone ever have contact with the SFLC[1]? They even have a IRC
New Zealand "Taumatawhakatangihangakoauauotamateaturipuk
akapikimaungahoronukupokaiwhenuakitanatahu" was also not bad... ;)
(TRANSLATION: “The brow of the hill where Tamatea, with the bony knees,
slid and climbed mountains. The great traveler sat and played on the
flute to his beloved.”)
On
Hi
Ok I went with Giovanni's suggestion of Capiopo for this release - see
the new splash screen in trunk.
Regards
Tim
On Sun, Oct 17, 2010 at 10:42 AM, Benoit de Cabissole
wrote:
>
>
> On 17/10/2010 10:37, Tim Sutton wrote:
>> Hi
>>
>> On Sun, Oct 17, 2010 at 10:16 AM, Vincent Leong wrote:
>>
On 17/10/2010 10:37, Tim Sutton wrote:
> Hi
>
> On Sun, Oct 17, 2010 at 10:16 AM, Vincent Leong wrote:
>> How about hill names as release names?
>> Hills is better than mountains because mountains is always too well
>> known and probably been used by others.
>> Moreover, their shape can be used
Hi
On Sun, Oct 17, 2010 at 10:16 AM, Vincent Leong wrote:
> How about hill names as release names?
> Hills is better than mountains because mountains is always too well
> known and probably been used by others.
> Moreover, their shape can be used to differentiate releases.
>
> One example: Bohol
Hi
On Sun, Oct 17, 2010 at 1:07 AM, Alex Mandel wrote:
> I agree that real place names is a better idea. I could see lots of
> Mythical/Fictitious names actually being claimed by people. I will also
> point out that the Mozilla Foundation uses National Parks/Reserves in
> the code naming of pre
I agree that real place names is a better idea. I could see lots of
Mythical/Fictitious names actually being claimed by people. I will also
point out that the Mozilla Foundation uses National Parks/Reserves in
the code naming of pre-release firefox branches and suggest that we
could do something wi
How about making release names geographic. QGIS 1.6 "Moscow" sounds
good and easily memorizable.
Maxim
Вы писали 16 октября 2010 г., 14:07:10:
TS> Hi
TS> On Sat, Oct 16, 2010 at 8:09 PM, Jürgen E. wrote:
>> Hi Tim,
>>
>> On Sat, 16. Oct 2010 at 01:42:54 +0200, Tim Sutton wrote:
>>> We (the PSC
Hi
On Sat, Oct 16, 2010 at 8:09 PM, Jürgen E. wrote:
> Hi Tim,
>
> On Sat, 16. Oct 2010 at 01:42:54 +0200, Tim Sutton wrote:
>> We (the PSC) recently received a threat of legal action against our
>> use of the word 'Tethys' in the naming of the 1.5 release of QGIS.
>> It seems that the word Tethy
Jürgen E. Fischer wrote:
Hi Tim,
On Sat, 16. Oct 2010 at 01:42:54 +0200, Tim Sutton wrote:
We (the PSC) recently received a threat of legal action against our
use of the word 'Tethys' in the naming of the 1.5 release of QGIS.
It seems that the word Tethys is trademarked by a company in one coun
Hi Tim,
On Sat, 16. Oct 2010 at 01:42:54 +0200, Tim Sutton wrote:
> We (the PSC) recently received a threat of legal action against our
> use of the word 'Tethys' in the naming of the 1.5 release of QGIS.
> It seems that the word Tethys is trademarked by a company in one country.
> Although we fee
Dear QGIS developers
We (the PSC) recently received a threat of legal action against our
use of the word 'Tethys' in the naming of the 1.5 release of QGIS. It
seems that the word Tethys is trademarked by a company in one country.
Although we feel their case is weak, we do not have the time, money
43 matches
Mail list logo
