[josm-dev] how does the transition to tested work ?
Sebastian Klein
bastikln at googlemail.com
Mon Mar 8 16:21:27 GMT 2010
Ævar Arnfjörð Bjarmason wrote:
>> #4584 (cursor not show in textfields of relations-editor) Cannot
>> reproduce. We don't have enough info to fix this.
>
> I think this is the same issue as I've just described in this bug
> report: https://josm.openstreetmap.de/ticket/4686
If it actually is the same issue, then it might be possible to fix it.
(This "broken" state seems to be the default behavior of a Java table.)
>> #4631 (Plugin download broken) [3090] should have addressed most
>> points of this ticket.
>>
>> #4401 (JOSM does not remember what has been uploaded) It's more
>> like an enhancement. Too complicated, will be fixed after release.
>
> I've used JOSM a lot recently to upload objects in the "one object at
> a time" mode, if it fails with a conflict it will start the whole
> thing over again (even if it doesn't need to).
This is news to me. Just tried the little "test script" from Karl in
"one object at a time" mode and it worked well. (I.e. it created a
conflict and the objects that had been uploaded before, where not marked
as "modified" anymore.
I would appreciate, if you could describe a way to reproduce.
>> #4371 (Changeset comment reverts to previous when switching
>> options) The blocker flag wasn't set by a developer. Should be
>> fixed, but isn't all that serious.
>
> FWIW I have at least 10 large changesets uploaded to the main API
> that have inaccurate changeset summaries because of this and related
> bugs.
I attempted to fix this once, but gave up soon. All these listeners
firing back and forth - it was frustrating to debug. Maybe you could
have a look, Karl? :)
__
Sebastian
More information about the josm-dev
mailing list