2011/12/29 Richard Weait
> That bug from 2008 pointed to my problem. I was using an old jre.
> Don't do that. :-)
>
>
Maybe we can do something about it in JOSM.
First I have updated this wiki page:
http://josm.openstreetmap.de/wiki/Help/SystemRequirements
To point out the more recent bugs cau
On Thu, Dec 29, 2011 at 3:26 PM, Richard Weait wrote:
> and a pointer to a similar error report in java "Problem with
> StAXValidatorHelper"
> http://www.java.net/node/666283
That bug from 2008 pointed to my problem. I was using an old jre.
Don't do that. :-)
_
Discussion on #osm-dev lead to this from josm with no ~/.josm directory.
Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2011-12-19 02:32:42
Last Changed Author: Don-vip
Revision: 4667
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
URL: http://josm.openstreetmap.de/svn/trunk
L
Dear All,
How does one run josm tested? r4667 complains of a errors in the
preferences file.
I have:
- removed .josm directory
- started josm-tested (complains of errors in the preferences file.
Should this say "no preferences file found. creating new preferences
file" ?)
- add my plugins
- clo
Hi,
We have released 4021 as a new tested version.
The problem regarding the Licence Change Phase III is (hopefully) fixed. Please
keep the repository stable until the changes to the server are implemented, so
we can add a point release if necessary.
Paul
__
Dirk Stöcker wrote:
Hello,
a new month means a new tested. There have been no new features, bot
only minor improvements and bug fixes in the last time. It seems nothing
prevents a new tested version now. Core translations of the major
languages are also nearly complete.
What about making JO
Hi,
Bodo Meissner wrote:
>>> There could also be one in each dialog when a translation into the
>>> current locale was not found.
>> No. That is not a good idea.
> Why not?
Because JOSM is primarily aimed at users, not developers or translators.
Bye
Frederik
--
Frederik Ramm ## eMail frede
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 16.06.2010 16:55, schrieb Dirk Stöcker:
> On Wed, 16 Jun 2010, Matthias Julius wrote:
>> A link to Launchpad
[...]
>> There could also be one in each dialog when a translation into the
>> current locale was not found.
>
> No. That is not a good id
On Wed, 16 Jun 2010, Matthias Julius wrote:
> Claudius writes:
>
>> Talking from a translator's (contributing to other projects as well
>> besides JOSM) perspective: I don't see the need for a string freeze and
>> am totally okay with way l10n is currently handled in a "live" manner.
>
> I just w
Claudius writes:
> Talking from a translator's (contributing to other projects as well
> besides JOSM) perspective: I don't see the need for a string freeze and
> am totally okay with way l10n is currently handled in a "live" manner.
I just would like to avoid that translations are invalidated
Am 13.06.2010 16:54, Dirk Stöcker:
> Here is the major problem:
> - We do not have really anyone who is responsible or even the contact
> addresses of translators
> - New translators are coming, others going.
> - Each translator seems to be active a short time only (except me, which
> is ti
Russ,
Russ Nelson wrote:
> It's not an opinion that JOSM doesn't do releases. It's a fact.
Can you elaborate. I mean, since Dirk took over, he at least makes a
point of "feature freezing" a "tested" version every few weeks or so,
asking developers to fix bugs before the current SVN is declared
Dirk Stöcker writes:
> Well actually I know two types of contributors:
> - people who start contributing and fix problems,
> - people who complain and do nothing.
>
> Sorry, but I value the opinion of the first set of people much higher.
It's not an opinion that JOSM doesn't do releases. It
On Mon, 14 Jun 2010, Ulf Lamping wrote:
> I'm not argueing that the JOSM releases could possibly be improved, but
> your "flame style" argumentation is not going to achieve a lot here ...
Sure, everything can be improved, but what needs improvement and how?
Maybe I should add my point of view as
On Sun, 13 Jun 2010, Russ Nelson wrote:
> my open source projects, and my users love it. Google for "russ
> nelson". JOSM is very much the outlier.
I did and when you are the "Russ Nelson" I found by this Google search I
don't think I like you or your opinions.
> > BTW: I miss the massive wor
Am 14.06.2010 00:45, schrieb Russ Nelson:
> Dirk Stöcker writes:
> > Everything you tell in your mail tells me several things:
> > a) You have absolutely no knowledge of JOSM release process
>
> There IS NO RELEASE PROCESS. That's what I'm trying to tell you. You
> don't do releases. You j
Ævar Arnfjörð Bjarmason writes:
> I think JOSM's release process is awesome. Projects like JOSM that do
> monthly releases tend to constantly keep the code in what's basically
> a ready-to-release state. I actually don't use the releases, I just
> track trunk.
And how was trunk for you when un
Dirk Stöcker writes:
> Everything you tell in your mail tells me several things:
> a) You have absolutely no knowledge of JOSM release process
There IS NO RELEASE PROCESS. That's what I'm trying to tell you. You
don't do releases. You just bless SVN versions. Where's the
changelog? How do p
On Sun, 13 Jun 2010, Russ Nelson wrote:
> This works. It's a pain, but it works. You have to have somebody who
> acts as a release manager. They have to be willing to prod people
> into action, to follow up, to make the announcements everywhere, to
> check and double-check. If you don't do thi
On Sun, 13 Jun 2010, Frederik Ramm wrote:
> I'm not too much into how Debian/Ubuntu work but don't they have the
> concept of a package maintainer who is usually not part of the software
> project in question, but just decides which version of the software he
> packages with which version of the r
On Sun, Jun 13, 2010 at 16:49, Russ Nelson wrote:
> Matthias Julius writes:
> > I am not saying we should hold development until all translations are
> > complete. I would just like to give translators a chance to get their
> > translation into a released JOSM.
>
> JOSM has never been released
Hi,
Russ Nelson wrote:
> Or, to put it another way, the JOSM release process is broken. JOSM
> is never released. People are simply told that a certain SVN version
> is better than other versions, and that version gets compiled for
> them. That's IT. As a former release manager for several proj
Matthias Julius writes:
> I am not saying we should hold development until all translations are
> complete. I would just like to give translators a chance to get their
> translation into a released JOSM.
JOSM has never been released.
Or, to put it another way, the JOSM release process is brok
Frederik Ramm writes:
> Hi,
>
> Matthias Julius wrote:
>> We don't really have to stop development, but maybe we can restrain
>> from introducing new features for a few days. Bug fixes are always
>> welcome as long as they don't change translated strings.
>
> Developers must never be held back f
On Sun, 13 Jun 2010, Matthias Julius wrote:
> All I am suggesting is to make this a bit more explicit by saying
> something like "Translators: please update your translation now if you
> want it to be in the next release. Developer: please don't make any
> major changes and don't change any transl
Hi,
Matthias Julius wrote:
> We don't really have to stop development, but maybe we can restrain
> from introducing new features for a few days. Bug fixes are always
> welcome as long as they don't change translated strings.
Developers must never be held back from doing what they have to do by
Dirk Stöcker writes:
> On Fri, 11 Jun 2010, Matthias Julius wrote:
>
>> It might be a good idea to declare a feature and string freeze and
>> issue a call for translation updates for a few days before each
>> testing release. This would give translators a chance to catch up.
>> It might also boo
On Sat, 12 Jun 2010, Henry Loenwind wrote:
>> Having a bad translation v.s. no translation
>
> Let me just quote a (re-translated) translation from another program I
> have to use regularly:
>
> "to weld You from forms"
>
> Any idea what that menu item may do?
JOSM bugtracker also can be (and is)
On 12.06.2010 01:13, Ævar Arnfjörð Bjarmason wrote:
> Having a bad translation v.s. no translation
Let me just quote a (re-translated) translation from another program I
have to use regularly:
"to weld You from forms"
Any idea what that menu item may do?
cu
Henry
__
On Thu, 10 Jun 2010, Dirk Stöcker wrote:
In my eyes the current release is more stable and bug-free than any
release before, so tested can be set. Except in case translators do major
texts today I would vote for making todays nightly build tested tomorrow.
I forgot to say: I did so. 3329 is ne
On Sat, 12 Jun 2010, Frederik Ramm wrote:
>> Actually that is a very bad example, as the original translator was me and
>> the word you talk about was token. Your translation is much better than
>> mine was, but I did know what I translated and tried long to find a
>> good translation,
>
> Sorry t
Hi,
Dirk Stöcker wrote:
> Actually that is a very bad example, as the original translator was me and
> the word you talk about was token. Your translation is much better than
> mine was, but I did know what I translated and tried long to find a
> good translation,
Sorry then. But you agree th
On Fri, 11 Jun 2010, Ævar Arnfjörð Bjarmason wrote:
When I localized the OpenStreetMap website I picked Translatewiki over
Launchpad because it had a more active community. That seems to be
paying off when you compare the statistics:
https://translations.launchpad.net/josm/trunk/+pots/josm
On Sat, 12 Jun 2010, Frederik Ramm wrote:
> I recently changed the E->D translation on launchpad for a number of
> OAuth related items. I don't remember what the problem was exactly but
> it was clear that the translator did not know anything about how OAuth
> works, but just chose context-free tr
On Fri, Jun 11, 2010 at 22:39, Frederik Ramm wrote:
> Ævar Arnfjörð Bjarmason wrote:
>>
>> This wouldn't solve the issue of having 100% complete translations at
>> time of release. But it seems that for overall translation
>> completeness Translatewiki is working great for OSM. We both have
>> act
Hi,
Ævar Arnfjörð Bjarmason wrote:
> This wouldn't solve the issue of having 100% complete translations at
> time of release. But it seems that for overall translation
> completeness Translatewiki is working great for OSM. We both have
> active OSM contributors, and an active general translation c
On Fri, Jun 11, 2010 at 20:56, Dirk Stöcker wrote:
> This does not mean that when there is a chance to better motivate our
> translators we shouldn't try it.
>
> ... Giving each of them a free copy of the software?
When I localized the OpenStreetMap website I picked Translatewiki over
Launchpad b
On Fri, 11 Jun 2010, Matthias Julius wrote:
>> In my eyes the current release is more stable and bug-free than any
>> release before, so tested can be set. Except in case translators do major
>> texts today I would vote for making todays nightly build tested tomorrow.
>
> It might be a good idea t
On Fri, 4 Jun 2010, Sebastian Klein wrote:
In my eyes the current release is more stable and bug-free than any
release before, so tested can be set. Except in case translators do major
texts today I would vote for making todays nightly build tested tomorrow.
Ciao
--
http://www.dstoecker.eu/ (P
Dirk Stöcker wrote:
> Status: We are down to 143 core bugs.
>
> The most important ones again in one list:
>
> #4832 - Ask before download plugins with newer JOSM version
> #5078 - draw areas below ways, selections above, filtered below
> #4142 - Missing relations when loading elements
> #4998 -
On Tue, 1 Jun 2010, Dirk Stöcker wrote:
I would like to have following issues fixed before it:
Two regressions:
#4832 - JOSM should again ask before downloading plugins which will not
work (it should be allowed, as user may also want to update JOSM before
restart itself)
#5078 - draw areas be
2010/6/1 Dirk Stöcker :
> #5086 - take care that we do normally download elements without their
> relations.
At the same priority for data integrity:
#4998 - Impossible to select nodes with filter
Ciao André
___
josm-dev mailing list
josm-dev@openstre
Hello,
it is time for a new tested.
I would like to have following issues fixed before it:
Two regressions:
#4832 - JOSM should again ask before downloading plugins which will not
work (it should be allowed, as user may also want to update JOSM before
restart itself)
#5078 - draw areas below
On Wed, 21 Apr 2010, Dirk Stöcker wrote:
If no bigger problems are reported till friday, then new development cycle
may start at friday and we move to Java6.
Actually we have a critical bug: #4929 - filtered objects are selectable.
This should be fixed soon.
Ciao
--
http://www.dstoecker.eu/
Hello,
I set tested to 3196 yesterday.
If no bigger problems are reported till friday, then new development cycle
may start at friday and we move to Java6.
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
___
josm-dev mailing list
josm-dev@open
Dirk Stöcker writes:
> Hello,
>
> even if I'm still not 100% happy with current JOSM I would think we should
> make 3070 tested, wait for reports and maybe make comming saturday
> version tested again and afterwards start with new development.
>
> Comments, objections?
I guess it is an improve
Hello,
even if I'm still not 100% happy with current JOSM I would think we should
make 3070 tested, wait for reports and maybe make comming saturday
version tested again and afterwards start with new development.
Comments, objections?
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
___
Hello all,
time for a new josm tested. After Karl added lots of news with the OAuth
stuff I think now the code consolidation and bug fixing phase should
start.
So
- please reduce the number of new or changed translatable strings
- please no bigger new features
- lots of bug fixing please
Hello,
I set tested to 2561. As I want a stable last Java5 version and I think
current tested version does not fullfill that to 100% (i.e. stable must
last probably 2 years :-), the next version will still be Java 5.
Java 6 will be introduced after next release (i.e. somewhen in January).
So
> There isn't so much new stuff a normal user will see, but I hope we
> reached a feels better, is faster, is stable state :-)
The new code base is looking good.
I'm not sure I followed the right procedure, but there is a new exception
bug in today's josm-latest 2542; I attached to ticket
On Fri, 27 Nov 2009, Dirk Stöcker wrote:
Still 194 bugs left.
We are down to 161 defects left (many old bugs closed).
Down to 147 :-)
Even if I sometimes sound a bit harsh I really appreciate all the work
which has been done in last JOSM release. I think you all did a pretty
good job:
Im Auftrag von Dirk Stöcker
Gesendet: Freitag, 27. November 2009 23:24
An: josm-dev@openstreetmap.org
Betreff: Re: [josm-dev] JOSM Tested!
On Wed, 25 Nov 2009, Dirk Stöcker wrote:
>> We have 234 bugs open, there should still plenty of work left.
>
> Still 194 bugs left.
We are down to 1
Dirk Stöcker wrote:
> a) Security issues. When you launch an application you must be sure it is
> really the right one.
>
Isn't it similarly insecure to run binary plugins that are located in
the user's home folder?
Btw., to address the memory problem, josm could exec itself on start
with a
On Sat, 28 Nov 2009, Sebastian Klein wrote:
>> Jiri fixed #3920. Means #3772 is left.
>
> What is the problem with launching the help browser as a new process?
> Seems fine to me.
a) Security issues. When you launch an application you must be sure it is
really the right one.
b) Installation issu
Dirk Stöcker wrote:
>
> Jiri fixed #3920. Means #3772 is left.
What is the problem with launching the help browser as a new process?
Seems fine to me.
(At least all gnome apps do it this way and it's quite customary in the
Windows world, too.)
from the ticket:
> Idea how to solve: Set help di
On Wed, 25 Nov 2009, Dirk Stöcker wrote:
We have 234 bugs open, there should still plenty of work left.
Still 194 bugs left.
We are down to 161 defects left (many old bugs closed).
I think at least #3920, #3772 should be fixed before release.
Jiri fixed #3920. Means #3772 is left.
The
On Tue, 17 Nov 2009, Dirk Stöcker wrote:
We have 234 bugs open, there should still plenty of work left.
Still 194 bugs left.
I think at least #3920, #3772 should be fixed before release.
But JOSM latest seems to be much more stable then last time when I tried
to announce a tested, so I thin
Hello,
I really appreciate the infrastructure work in JOSM, but users also want
to see progress, so please slow down a bit and do a bit bug fixing.
Please:
- No interface text changes in next two weeks if not really necessary.
- No more redesigns yet.
- No new features (except small ones)
On Sat, 03 Oct 2009 11:53:10 +0200, Karl Guggisberg
wrote:
>> I was hoping to be developing over the weekend. I'm going to add
>> referrers
> (so you can eg get list of ways that reference
>> some node). That should make some parts of josm much faster when working
> with large datasets.
> Great
On Sat, 3 Oct 2009, Dirk Stöcker wrote:
So start your development with assumption in mind that 2221 will get
tested on sunday. :-)
Ok, I made 2221 tested now. Please don't do any corrupting checkins today
(delay them to tomorrow after 4AM), so I have the chance to make the
nightly build of t
On Sun, Sep 27, 2009 at 10:04 PM, Dirk Stöcker
wrote:
> Are there any critical things left? I think no, but if you think so, then
> tell the bug report number.
Perhaps this qualifies: http://josm.openstreetmap.de/ticket/3644
___
josm-dev mailing list
j
works for me, too, thanks!
-- Karl
-Ursprüngliche Nachricht-
Von: josm-dev-boun...@openstreetmap.org
[mailto:josm-dev-boun...@openstreetmap.org] Im Auftrag von Dirk Stöcker
Gesendet: Samstag, 3. Oktober 2009 12:22
An: josm-dev@openstreetmap.org
Betreff: Re: [josm-dev] JOSM Tested
On Sat
On Sat, 3 Oct 2009, Karl Guggisberg wrote:
>> Should a new tested be released sunday evening?
> I wouldn't do it.
>
> I'm not worried about #3459 and #3575, but like Claudius I feel that the new
> MultiSplitLayout needs more testing, see #3640 for instance.
Fixed this one. Thought it was a bug in
On Sat, 3 Oct 2009, Jiri Klement wrote:
> I would preffer to have new tested released asap, the best would be
> releasing #2221 right now :-). I was hoping to be developing over the
> weekend. I'm going to add referrers (so you can eg get list of ways
> that reference some node). That should make
DataSet and
CollectBackReferencesVisitor obsolete.
-- Karl
-Ursprüngliche Nachricht-
Von: josm-dev-boun...@openstreetmap.org
[mailto:josm-dev-boun...@openstreetmap.org] Im Auftrag von Jiri Klement
Gesendet: Samstag, 3. Oktober 2009 11:48
An: josm-dev@openstreetmap.org
Betreff: Re: [josm-dev] JOSM Test
I would preffer to have new tested released asap, the best would be
releasing #2221 right now :-). I was hoping to be developing over the
weekend. I'm going to add referrers (so you can eg get list of ways
that reference some node). That should make some parts of josm much
faster when working with
On Sat, 3 Oct 2009, Karl Guggisberg wrote:
>> Should a new tested be released sunday evening?
> I wouldn't do it.
>
> I'm not worried about #3459 and #3575, but like Claudius I feel that the new
> MultiSplitLayout needs more testing, see #3640 for instance.
Ok, ok, my fault. I really thought this
streetmap.org
[mailto:josm-dev-boun...@openstreetmap.org] Im Auftrag von Dirk Stöcker
Gesendet: Freitag, 2. Oktober 2009 22:20
An: josm-dev@openstreetmap.org
Betreff: Re: [josm-dev] JOSM Tested
I wrote on Mon, 28 Sep 2009,
>> please do not develop or checkin new stuff in next time so code can
&g
On Fri, 2 Oct 2009, Claudius wrote:
please do not develop or checkin new stuff in next time so code can
mature
a bit (but do bugfixes instead :-). If no larger bugs show inbetween I
would say the next tested version should be released next weekend.
>>>
>>> Ok, we had som
Am 02.10.2009 22:19, Dirk Stöcker:
> I wrote on Mon, 28 Sep 2009,
>
>>> please do not develop or checkin new stuff in next time so code can mature
>>> a bit (but do bugfixes instead :-). If no larger bugs show inbetween I
>>> would say the next tested version should be released next weekend.
I wrote on Mon, 28 Sep 2009,
>> please do not develop or checkin new stuff in next time so code can mature
>> a bit (but do bugfixes instead :-). If no larger bugs show inbetween I
>> would say the next tested version should be released next weekend.
>
> Ok, we had some critical bugs fixed this
Am 28.09.2009 00:04, Dirk Stöcker:
> On Sun, 20 Sep 2009, Dirk Stöcker wrote:
>
>> please do not develop or checkin new stuff in next time so code can
>> mature
>> a bit (but do bugfixes instead :-). If no larger bugs show inbetween I
>> would say the next tested version should be released next wee
---
From: "Dirk Stöcker"
Sent: Sunday, September 20, 2009 7:15 AM
To:
Subject: [josm-dev] JOSM Tested
> Hello,
>
> please do not develop or checkin new stuff in next time so code can mature
> a bit (but do bugfixes instead :-). If no larger bugs show inbetween I
> would say th
Hello,
please do not develop or checkin new stuff in next time so code can mature
a bit (but do bugfixes instead :-). If no larger bugs show inbetween I
would say the next tested version should be released next weekend.
Translators please continue translating - I fixed lots of typos in the
sof
2009/8/15 Pieren :
> On Fri, Aug 14, 2009 at 11:31 PM, Dirk
> Stöcker wrote:
>> Hello,
>>
>> It was a long time since last tested version. Are there (beside missing
>> translations) any reasons not to make the latest to tested in next days?
>>
>> Ciao
>
> Any chance to find a solution about #3181 b
On Fri, Aug 14, 2009 at 11:31 PM, Dirk
Stöcker wrote:
> Hello,
>
> It was a long time since last tested version. Are there (beside missing
> translations) any reasons not to make the latest to tested in next days?
>
> Ciao
Any chance to find a solution about #3181 before the release ?
Since some
Hello,
It was a long time since last tested version. Are there (beside missing
translations) any reasons not to make the latest to tested in next days?
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
___
josm-dev mailing list
josm-dev@openstree
77 matches
Mail list logo
