[josm-dev] how does the transition to tested work ?

[Sebastian Klein]

colliar wrote:
> I still wonder how the transition to tested works. As bug #4666
> is/was really annoying but is fixed now exists still in r3070. This
> has also effects on "update data" (see #4663). Please update tested
> to r3081.

Dirk suggested that we "maybe make comming saturday version tested
again". (Which would be last Saturday, by now.)

There seem to be no updates on that, so who knows what will happen.

> I also find 5 bugs left with keyword: "r-2010-01-blocker". Are you
> planning to solve them before working on upstream ?

Short comments on the "r-2010-01-blocker" tickets:

#4366 (validator: repair: overlapping ways distroys data)
   Plugin issue, can be fixed after release.

#4584 (cursor not show in textfields of relations-editor)
   Cannot reproduce. We don't have enough info to fix this.

#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.

#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.

So, I'd say it was OK to release, but tested version should be updated 
before next development cycle.

> I think tested should be a version without any blocker/critical bug
> reported on and being tested as unstable/latest for a week.

This is how we try to do it, but some critical bus are not easy to fix,
so we postpone these issues and move on.

__

Sebastian