Re: [josm-dev] Endless bugfixing
Hello, May I make a suggestion? create a java 6.0 branch and run that in parallel until it works. mike ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Endless bugfixing
On Thu, 11 Mar 2010, jamesmikedup...@googlemail.com wrote: May I make a suggestion? create a java 6.0 branch and run that in parallel until it works. As nobody would care for 5.0 branch then, we can also leave it as is. As already said I'm not perfectly happy with current tested and it took/takes longer due to this 6.0 Java issue. But it does not take endless :-) End of this month is JAVA6.0 in any case. It would be fine, when we have a bit more stable version by then, but if not, then current tested will be last 5.0. Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Endless bugfixing
Hi, Dirk Stöcker wrote: End of this month is JAVA6.0 in any case. It would be fine, when we have a bit more stable version by then, but if not, then current tested will be last 5.0. I have taken the liberty of posting that bit to talk@ so that those who don't yet use Java6 have some time to get prepared (i.e. order a new Macbook) ;-) Bye Frederik ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
[josm-dev] Endless bugfixing (was: Plugins not working with 3094 and Linux ?)
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
Re: [josm-dev] Endless bugfixing (was: Plugins not working with 3094 and Linux ?)
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
Re: [josm-dev] Endless bugfixing
Karl Guggisberg wrote: 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? I mean #4705. If you think there are no more problems, then it's fine. 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. So it is simply a misunderstanding as i think we are not there yet, and still stuck with bugfixing. So sorry about false accusations, I don't know who is to blame. Actually the developer wiki page was quite useful for tracking status. 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 Which implies for me, there are no new features before that. (Of course the mail came after the commit.) __ Sebastian ___ josm-dev mailing list josm-...@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Endless bugfixing
On Wed, 10 Mar 2010, Sebastian Klein wrote: 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. Also there seems to be some central drawing and data loss issues. As said I have little time to do deep investigations, but: - I see the bug reports and see little progress in reduction - Whenever I start JOSM myself I detect serious issues still existing or new - We have really lots of open core bugs - Discussions show me there are still issues which should be fixed before doing fancy new stuff - Plugin handling still does not work as reliable as it did before (does e.g. not load plugins from system files - see bugreport recently created). This is a very central component and must work reliable. So my feeling is: JOSM is not stable enough. If you and other more active users reach a consensus that my feeling is false, then I will accept that and we can move on. Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
