Hi I'm only aware of one defect related to 3102 (Sebastian, you've reported it today) and this one is fixed. What other defects related 3102 are you referring to? Actually 3102 has been *fixing* four defects (or closing two tickets and fixing two unreported defects). I've added a warning when I checked in 3102 because I knew that there was some risk but from my interpretation JOSM is currently exactly in the phase where these risks are taken.
My interpreation was that a tested was pushed out (~ a week ago it appeared on the JOSM home page) and that JOSM started another of JOSMs traditional "cylces". If the question is whether we "really need this right now", then my intrpretation would be: yes,that's exactly how people have been working on JOSM in the past. From my point of view JOSM would currently focus on new features and larger reworks before another stabilization phase towards the end of such a "cycle". I don't like the traditional approach of JOSM developoment enough to advocate it, though. I'd be happy if things changed. From todays emails I learned about the following plan: * there is yet another "tested" planned for end of this month latest, perhaps for next friday * it's going to be the long announced last "tested" for Java 5 Regards Karl Am 10.03.2010 19:00, schrieb Sebastian Klein: > Dirk Stöcker wrote: > >> JOSM should be a bit more stable, but I also don't like to wait >> endless. JAVA6 will come end of month latest and JAVA5 users will >> have to live with the version we have by then. Would be nice if the >> plugin issues and some other serious stuff can be fixed till then. If >> there are really bigger issues and users of JAVA5 have no other >> chance, then a bug-fix branch can be made if a maintainer for it can >> be found (which I doubt). >> >> If we have a very stable version tomorrow, then JAVA6 can come friday >> :-) >> > We are fixing bugs for 2 months now, so time can't be the issue. We have > to clearly identify the bugs that need to be fixed, then just do it and > move on. The new stuff is probably piling up in the local repositories, > this stagnation is quite annoying. > > So i can partly understand why Karl pushed out [3102] but it introduced > a couple of bugs and there may be more to come. Do we really need this > right now? > > And Dirk, you do the final decisions, so could you please be a little > more verbose and clearly state what you think needs to be fixed? > Especially if deadlines are missed, a status update wouldn't hurt. > > Happy coding :) > > __ > > Sebastian > > _______________________________________________ > josm-dev mailing list > josm-...@openstreetmap.org > http://lists.openstreetmap.org/listinfo/josm-dev > > _______________________________________________ josm-dev mailing list josm-...@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
