Re: [josm-dev] josm-tested (r4667) bad preferences file: SOLVED
2011/12/29 Richard Weait rich...@weait.com 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 caused by an old JRE version. Next, I propose to update the Main.checkJava6() to issue a warning when JOSM runs with an old JRE 6. We'd just have to define what old is. It must be at least 14 (the update fixing this issue), but we have the following versions of openjdk-6-jre in Debian/Ubuntu: - Debian stable: 18 - Ubuntu stable: 23 So, I'd suggest 18, to start with ? ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
[josm-dev] josm-tested (r4667) bad preferences file
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 - close - start josm-tested (complains of errors in the preferences file) What next? ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] josm-tested (r4667) bad preferences file
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 Last Changed Date: 2011-12-19 00:02:30 +0100 (Mon, 19 Dec 2011) Last Changed Rev: 4667 Warning: Missing preference file '/home/nerd/.josm/preferences.xml'. Creating a default preference file. ERROR: '' java.lang.NullPointerException at com.sun.org.apache.xerces.internal.jaxp.validation.StAXValidatorHelper.validate(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(Unknown Source) at javax.xml.validation.Validator.validate(Unknown Source) at org.openstreetmap.josm.data.Preferences.validateXML(Preferences.java:1436) and a pointer to a similar error report in java Problem with StAXValidatorHelper http://www.java.net/node/666283 ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] josm-tested (r4667) bad preferences file: SOLVED
On Thu, Dec 29, 2011 at 3:26 PM, Richard Weait rich...@weait.com 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. :-) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
[josm-dev] JOSM tested
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 ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM Tested
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 JOSM tested e.g. next wednesday? Ciao OK, would be nice to get the majority of relation types and their roles in the presets. People tend to take the validator warnings rather serious and there were a couple of complaints already. Sebastian ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
Claudius claudiu...@gmx.de 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 by a string change just before a release. A link to Launchpad already is on the MoTD page. We could also include one in the About dialog to enable people to find it later. There could also be one in each dialog when a translation into the current locale was not found. Matthias ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
On Wed, 16 Jun 2010, Matthias Julius wrote: Claudius claudiu...@gmx.de 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 by a string change just before a release. Well I talk to Launchpad for more than a year, that they should reintegrate a fuzzy handling, so that translators don't need to retranslate for minor changes (but only need to check and click). When others also report this continiously, then maybe it gets higher priority. 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. 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] JOSM-Tested
-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 idea. Why not? Bodo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkwZMe4ACgkQnMz9fgzDSqfr2QCfaQDSsZvjaqKMk8ctcQ2XQBdY 8WgAniTtfXs+U3S2ozdpZqn8Ja4Z8FZ5 =N2o3 -END PGP SIGNATURE- ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
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...@remote.org ## N49°00'09 E008°23'33 ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
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 tested and normal development continues. Nowaday the standard suggestion for the general public is to always use the latest tested rather than current SVN as it used to be. Granted, those tested versions don't have release numbers, but other than this rather superficial detail, what objective and factual criterion do they clearly not fulfil in order to be called releases? You *are* familiar with the current vs. tested scheme, are you not? Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33 ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
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 tied due to other reasons to the project). - Most of them aren't on josm-dev. 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. There are three triggers for me to contribute to JOSM translation: - I'm running nightly builds and if I spot an untranslated string I head over to launchpad - I'm reading this dev ML; whenever Dirk announces a new stable I check launchpad - every now and then I just check into JOSM's launchpad section and translate strings where I know the context just because I'm in the mood. We won't reach 100% string coverage this way, but even 60% is okay if the main interface gets done this way. We don't need 100% with every exception message translated. From my perspective the current discussion is a non-issue. Claudius ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
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 work on JOSM you did to improve the situation. There is no point in making a contribution which the developers reject. Been there, done that, it's a FWOMPT. If you guys don't want to do releases, I can't force you. 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. 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] JOSM-Tested
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 admin: - Current release is down to about 130 bugs, most of them special cases, debatable things or very hard to fix or unreproducable issues. Most other reports are suggestions (before release we had about 200 bugs). - About 70% of JOSM users have a 100% localized interface (which means de+en). About 20% have a 95%+ localized interface (ru,fr,it). - We get nearly no serious bug reports for tested versions. - We VERY seldom get exception reports and these mostly for latest after new features have been added. - We have a working nightly build, which is so stable, that a lot of people use it instead of the recommended tested. - Most reports we get are minor issues (thought not easy to fix). For me this is a good sign, as for faulty software nobody cares for minor issues. - We have approx. 50% of the OSM editor market. I can create different stats which show that JOSM is better, others that Potlatch is better, but altogether it is 50/50. Actually I don't see a reason to change the current development model. I agree, that communication for translations could be improved, but as already said I don't see how this can be done currently, as I don't know which people are our translators and it seems they change from time to time. This sounds a bit strange, but it works nevertheless. 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] JOSM-Tested
Dirk Stöcker openstreet...@dstoecker.de 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 boost their motivation a little bit when they know that their perfect 100% translation actually will make it into a release. Are there any translators on this list? How would you like that to be handled? Yes. I'am. I always tell me before release that everything must be translated. Usually I try to do so :-) That's a good first step. Now, you just need to tell the other translators as well. ;-) No really. Usually in the time after announcing tested stage first time only bug-fixes are done and they don't usually add new user visible strings, but mainly error messages or the like (or new plugin strings). I also take care that the translators have a chance to catch up before, so the languages which currently try the 100% (German, Ukrainian, Russian, Italian, ...) have the chance to do so. 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 translated strings. in your announcement of an upcoming release and give a deadline for this of a few days. Of course, this only helps if translators get to see the announcement. On the other hand JOSM is in flux always, so texts in updated plugins become outdated and many language miss newer strings anyways. Until now it seems impossible to get a release handling for JOSM translations. There are always only few people who really actively translate texts and most languages stay in the incomplete state. And there are really many strings in JOSM and always comming a lot of new strings. It is a bit weird that plugin localisation is done in JOSM core, but this is a different can or worms. I know this situation from other projects and it seems it is unsolvable, so I don't really want to stop development because of missing translations. Only solution would be a release branching each time we hav a tested, but due to various reason explained in length in other mails I still don't think the currently working josm process should be changed without need. 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. Maybe we could just not update Launchpad for a week or two after a -tested release. And if there are significant improvements in translations after that time we can still consider creating a branch and update the translations in -tested. This does not mean that when there is a chance to better motivate our translators we shouldn't try it. We can speculate about what would motivate translators forever. It would be good to get some input from actual translators (besides yourself). Matthias ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
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 translation. If a bug fix requires that a string be changed, then the string must be changed. Even if it is just a minor thing like an alert popup that is worded badly so people tend to misunderstand it - we cannot hold back improving the software just because the translator for Ancient Greek is on holiday. If people would rather have a software with more bugs but where everything has been translated, than one with less bugs but where some things are untranslated, then we really have to do branches for language versions. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33 ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
Frederik Ramm frede...@remote.org 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 from doing what they have to do by translation. If a bug fix requires that a string be changed, then the string must be changed. Even if it is just a minor thing like an alert popup that is worded badly so people tend to misunderstand it - we cannot hold back improving the software just because the translator for Ancient Greek is on holiday. 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. I imagine it could be very frustrating to find that a string shows up untranslated just because someone felt that a comma needed to be added. Do you think holding back string changes for a few (maybe 3?) days will disrupt development too much? The other question is of course whether there would be a significant improvement of translations accomplished within only a few days. If people would rather have a software with more bugs but where everything has been translated, than one with less bugs but where some things are untranslated, then we really have to do branches for language versions. Not every bug fix requires a string change and not every bug in strings is grave enough to invalidate all its translations in an upcoming release. Matthias ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
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 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 projects, this frustrates the bejeezus out of me. JOSM is under constant development is not a substitute for having releases. EVERYBODY works on their open source project every day. Don't think you're so special that you don't have to release code. So, if JOSM had a standard release process, then the developers would confer amongst themselves to decide if there are any major changes underway. If not, and the code is working reasonably well, then you fork it off into a release version and a development version. The clock starts ticking. Translators are told Please check your translation. Users are told Please download and test this. Contributors are told Check the documentation and bug reports. Developers keep working, but as they fix bugs, they check them into both the release version and the development version. 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 this, then you don't have a project. You just have code. Just as an extra thought, Mark Shuttleworth is trying to push open source folks into coordinating releases by date rather than by feature completion. Makes it MUCH easier for users because they get a big chunk of code, all of which is compatible with the other chunks and all of it is the latest and greatest. Anybody know what version of JOSM is in Ubuntu right now? And if we don't have a user focus, then we have no focus at all. NONE. ZERO. ZIPPO. NIL. NADA. Why am I so adament? Because except for the few projects we contribute to, WE ARE ALL USERS. Anybody here hacked on the Linux kernel? gcc? gtk? java? X? gpsd? Maybe you've contributed a little bit, but for the most part, for most things, we choose to be users. Drop by drop, the mill is turned, but if we don't make sure that OUR drop is the finest, the best, the most rounded drop ever, why should anybody else? -- --my blog is athttp://blog.russnelson.com Crynwr supports open source software 521 Pleasant Valley Rd. | +1 315-600-8815 Potsdam, NY 13676-3213 | Sheepdog ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
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 projects, this frustrates the bejeezus out of me. My instinct was to write: Why don't you act as our release manager then if you find this so damn important! But reading the rest of your email I thought, I'd rather not be managed by you ;) 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 rest? And if we don't have a user focus, then we have no focus at all. Maybe not having focus is the next big thing. I mean, it's not that JOSM development is somehow in a crisis, or is it? Anyway we only have to stick with it another few weeks until Potlatch 2 comes out and everbody flocks to that. (That's the nice thing about versions, you can have release parties every now and then.) Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33 ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
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 rest? Actually this is normal. I do same for muliple projects for openSUSE and I only participate in few of them. Usually you only package newest version and that's it. Sometimes you fix bugs and try to get them imported in upstream as soon as possible to reduce maintenance overhead. In a very few cases packaging is like branching (expecially if upstream has strange opinions about how bugs should be handled or what should be defined as bug). 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] JOSM-Tested
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 this, then you don't have a project. You just have code. Everything you tell in your mail tells me several things: a) You have absolutely no knowledge of JOSM release process b) You have no knowledge of different development models and OpenSource. c) You have no knowledge of motivation. What you describe is ONE and only one method how it can work. And actually I doubt this method works really good for OpenSource. I know only few projects which actually use this Old style commercial way of software development with success. There are lots of other methods and JOSM uses one of the other methods. You should read a lot about motivation, Opensource in general and programming models. I suggest you to learn a bit about eXtreme Programming - it is the closest to JOSM development model you may find. If you want I can tell you several good books one should have read to understand how and why programming is done. Contrary to you I don't know what's right or wrong, I only know what works or not and JOSM works - it is actively developed and used. I don't like flames like the letter you wrote and probably I should have ignored it as I usually try to do, but sometimes I can't, especially as currently I'm responsible for JOSM development, so your flames were directed at me personally. I've heard it so often: OpenSource can't work, its not organized. Wikipedia can't work, no one controls it. OpenStreeMap can't work, people can't be surveyors. Maybe I can't say why it works, but at least I do understand that it works. BTW: I miss the massive work on JOSM you did to improve the situation. 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] JOSM-Tested
Æ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 undo didn't? But the releases aren't just an arbitrary monthly snapshot. The devs make an effort to close any remaining blocker bugs before a release, but of course with everyone being a volunteer that doesn't always get done optimally. There's a lot of grunt work to be done in a release, and ... it's not happening with JOSM. I'm not volunteering, but I AM trying to point out what is missing, since some people don't seem to understand why translations don't just magically appear. Of course there are some things that could be done better, like a translation freeze a few days before release. A few days? That's optimistic. A month is a minimum. In my experience. Of course, Dirk thinks I have no experience, so that's kinda wasted breath. Small-ish projects like JOSM can actually become much worse for their users if they do proper releases. I.e. something where there's a maintenance branch that gets maintained in paralell, and things only get merged there once they're sure to work. Doing stuff like that takes a lot of manpower. My point exactly. It's hard to do releases. Don't call what JOSM does a release. JOSM does snapshots. -- --my blog is athttp://blog.russnelson.com Crynwr supports open source software 521 Pleasant Valley Rd. | +1 315-600-8815 Potsdam, NY 13676-3213 | Sheepdog ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
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 just bless SVN versions. Blessing SVN versions would already be one possible release process. Even telling your users use the latest SVN sources and compile your own binary *is* in fact a (the smallest possible?) release process - every SVN version is it's own release. BTW: Dirk does more than just blessing SVN versions. Please replace your JOSM don't have a release process with JOSM don't have the release process I know from other projects / would like to see. I know from my daily work that having such a classical release process (that you seem to have in mind) can be a *lot* of additional effort. Unless you have someone who wants to spend this effort in his spare time / get paid for it, the discussion about whats best for your users is pretty much pointless. 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 ... Regards, ULFL ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
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 translations of the terms involved. This resulted in a very skewed overall picture. The person did have an OSM background but it seems no OAuth knowledge. 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, but translating is a kind of art and not always is the first try the best result. Sometimes it needs more iterations of different people to get a good result. 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] JOSM-Tested
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 http://translatewiki.net/wiki/Translating:OpenStreetMap/stats/trunk Actually I have lots of troubles with that. - How many strings are actually translated? The percentage says nothing at all. JOSM had 100% percentage several times for many languages. - How many new strings are comming in - How is the translators interface? upload/download of .po files - I found no reliable search interface - How are fuzzy strings handled - i.e. what is when input strings change only slightly? To me translatewiki seems to be much more complicated for translators than launchpad is (which has still lots of quirks, e.g. the missing fuzzy string handling). I'm not tied to launchpad and would like to switch to a better interface (althought I invested lots of work to get launchpad better). But it really must be better. 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] JOSM-Tested
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 that making good translations in the JOSM context will in all but the most primitive cases require an OSM background? Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33 ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
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 new tested. 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] JOSM-Tested
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 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 boost their motivation a little bit when they know that their perfect 100% translation actually will make it into a release. Are there any translators on this list? How would you like that to be handled? Yes. I'am. I always tell me before release that everything must be translated. Usually I try to do so :-) No really. Usually in the time after announcing tested stage first time only bug-fixes are done and they don't usually add new user visible strings, but mainly error messages or the like (or new plugin strings). I also take care that the translators have a chance to catch up before, so the languages which currently try the 100% (German, Ukrainian, Russian, Italian, ...) have the chance to do so. On the other hand JOSM is in flux always, so texts in updated plugins become outdated and many language miss newer strings anyways. Until now it seems impossible to get a release handling for JOSM translations. There are always only few people who really actively translate texts and most languages stay in the incomplete state. And there are really many strings in JOSM and always comming a lot of new strings. I know this situation from other projects and it seems it is unsolvable, so I don't really want to stop development because of missing translations. Only solution would be a release branching each time we hav a tested, but due to various reason explained in length in other mails I still don't think the currently working josm process should be changed without need. 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? ... (hmm, wrong development model :-) 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] JOSM-Tested
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 community contributing. To be honest I'm not keen on having anything translated by members of a general translation community. There are many things which, I believe, need the OSM context to be translated properly. 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 translations of the terms involved. This resulted in a very skewed overall picture. The person did have an OSM background but it seems no OAuth knowledge. I would expect many more problems of that caliber to show up if we let people without OSM exposure translate stuff. It may just about work for the web site (but even there I'm skeptical) but not for a sophisticated editor. In my eyes, a *bad* (or half-good) translation is worse than no translation at all. If members of the JOSM or at least OSM community do not have the time to translate JOSM into Ancient Greek then I'd prefer not to have an Ancient Greek JOSM at all, rather than having an Ancient Greek JOSM which has been translated by Ancient Greek enthusiast who knew nothing of OSM. Unfortunately the statistics capture quantity, not quality. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33 ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
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/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM-Tested
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 below ways and draw empty ways according to area style Both still there, one part of #5078 fixed a rather recent one: #5086 - take care that we do normally download elements without their relations. Was duplicate of #4142. 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 - Impossible to select nodes with filter 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] JOSM-Tested
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 - Impossible to select nodes with filter #4998 should be fixed, but still requires some testing. I don't know if there is a ticket for this, but a related major problem is how to prevent someone from deleting a node that is still part of a hidden way. The new connected style for nodes (enlarged square) gives a hint in many cases, but I guess that is not enough. A first step would be a visual indication that a node is used by filtered objects. Any suggestions how this could look like? Sebastian ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
[josm-dev] JOSM Tested now 1196
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@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
[josm-dev] JOSM Tested
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) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM Tested
Dirk Stöcker openstreet...@dstoecker.de 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 improvement over the current tested in any case. Matthias ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM Tested!
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: - structural changes which have been necessary for some time - many fixes regarding smaller user interface issues - some new features 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 :-) Thanks to all the contributors. Timeline: - Monday version gets tested - When no serious issues pop up in bug tracker: - The code rework allowed phase starts Wednesday - Probably Wednesday version will be set to tested as well 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] JOSM Tested! [#3772 - Help browser calling external program]
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 issues. Java must be installed in a way, that you can launch it. c) Does not work in Webstart variant or as applet. from the ticket: Idea how to solve: Set help dialog modal and modal dialog non-modal when help from modal dialog is called. I think a modal help dialog is not so good, because users like to keep it open in the background for future reference. But it is the only solution I can think of which works. And closing the help dialog to continue is much better than introducing lots of design trouble. Whenever we switch to Java 6, we can solve that issue with different modal modes as supported by Java 6. 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] JOSM Tested! [#3772 - Help browser calling external program]
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 better -Xmx... parameter... *ducks runs* b) Installation issues. Java must be installed in a way, that you can launch it. True, but shouldn't be a problem in practice. (There are java apps that are run by a script. They must have figured this out somehow.) c) Does not work in Webstart variant or as applet. That's a problem... How many Webstart users are there? One could simply redirect the help to a browser window for these people. (Or use modal help for webstarters only.) from the ticket: Idea how to solve: Set help dialog modal and modal dialog non-modal when help from modal dialog is called. I think a modal help dialog is not so good, because users like to keep it open in the background for future reference. But it is the only solution I can think of which works. And closing the help dialog to continue is much better than introducing lots of design trouble. Whenever we switch to Java 6, we can solve that issue with different modal modes as supported by Java 6. Btw. may I ask what are the main reasons for using Java 5? (Other than support users that haven't updated their Java for 3 years.) __ Basti ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM Tested! [#3772 - Help browser calling external program]
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 dialog modal and modal dialog non-modal when help from modal dialog is called. I think a modal help dialog is not so good, because users like to keep it open in the background for future reference. __ Basti ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM Tested
On Sat, 03 Oct 2009 11:53:10 +0200, Karl Guggisberg karl.guggisb...@guggis.ch 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! Hopefully, this will make BackreferenceDataSet and CollectBackReferencesVisitor obsolete. Hello, I remade CollectBackReferencesVisitor about two weeks ago (now it is commited). See discusion at http://josm.openstreetmap.de/ticket/3475. Now it is much faster for more query (I have done it for child search). I am not saying, that the code would be faster without them. I am just noticing you, that some speed improvement has been already done. -- Petr Dlouhý ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM Tested
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. -- Karl -Ursprüngliche Nachricht- Von: josm-dev-boun...@openstreetmap.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 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 weekend, so I think the timeline should be expanded a bit to verify if fixes are correct. So expect next tested somewhen mid or end of next week. Are there any critical things left? I think no, but if you think so, then tell the bug report number. and now I have a problem. We had critical bug-fixes again which means another delay. But also if we continue this we wont get a tested at all, so I ask you all - Should a new tested be released sunday evening? Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM Tested
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 large datasets. On Sat, Oct 3, 2009 at 11:34 AM, Dirk Stöcker openstreet...@dstoecker.de wrote: 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 feature to be uncritical and worth to be in tested. We can make #2221 tested nevertheless if nobody sees troublesome bugs in it. Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM Tested
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! Hopefully, this will make BackreferenceDataSet 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 Tested 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 large datasets. On Sat, Oct 3, 2009 at 11:34 AM, Dirk Stöcker openstreet...@dstoecker.de wrote: 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 feature to be uncritical and worth to be in tested. We can make #2221 tested nevertheless if nobody sees troublesome bugs in it. Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM Tested
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 some parts of josm much faster when working with large datasets. Well, that is independent. You can start in any case, as tested phase means also slow development, so your code wont get out of sync even if you can't check it in). The problem is: when I do a tested with major bugs, then we need to start with bugfix releases and this is somehing I want to prevent because it is much additional work. So start your development with assumption in mind that 2221 will get tested on sunday. :-) 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] JOSM Tested
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 the MultiSplit code which I though has been tested otherwhere. 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] JOSM Tested
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, 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 the MultiSplit code which I though has been tested otherwhere. Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM Tested
On Sun, Sep 27, 2009 at 10:04 PM, Dirk Stöcker openstreet...@dstoecker.de 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 josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
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 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 weekend, so I think the timeline should be expanded a bit to verify if fixes are correct. So expect next tested somewhen mid or end of next week. Are there any critical things left? I think no, but if you think so, then tell the bug report number. and now I have a problem. We had critical bug-fixes again which means another delay. But also if we continue this we wont get a tested at all, so I ask you all - Should a new tested be released sunday evening? 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] JOSM Tested
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. Ok, we had some critical bugs fixed this weekend, so I think the timeline should be expanded a bit to verify if fixes are correct. So expect next tested somewhen mid or end of next week. Are there any critical things left? I think no, but if you think so, then tell the bug report number. and now I have a problem. We had critical bug-fixes again which means another delay. But also if we continue this we wont get a tested at all, so I ask you all - Should a new tested be released sunday evening? Sunday is a bit short, especially with the late incorporation of the right-hand size pane resizing [1]. What about making @2223 the tested? It seems it's missing some i18n though, but nothing major in my opinion. Claudius [1] http://josm.openstreetmap.de/ticket/3550 ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM Tested
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 some critical bugs fixed this weekend, so I think the timeline should be expanded a bit to verify if fixes are correct. So expect next tested somewhen mid or end of next week. Are there any critical things left? I think no, but if you think so, then tell the bug report number. and now I have a problem. We had critical bug-fixes again which means another delay. But also if we continue this we wont get a tested at all, so I ask you all - Should a new tested be released sunday evening? Sunday is a bit short, especially with the late incorporation of the right-hand size pane resizing [1]. What about making @2223 the tested? It seems it's missing some i18n though, but nothing major in my opinion. I don't think the resizing code is really critical, as the major components are tested in other products and we have two days to decide :-) The main question is if the last major bug fixes really catched the data detroying bugs. At least #3459 and #3575 are still there and these seem to be a bit critical. 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] JOSM Tested
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 weekend. Ok, we had some critical bugs fixed this weekend, so I think the timeline should be expanded a bit to verify if fixes are correct. So expect next tested somewhen mid or end of next week. Are there any critical things left? I think no, but if you think so, then tell the bug report number. Critical freeze issues using non-latin characters in upload comments: http://josm.openstreetmap.de/ticket/3371 Claudius ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
[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 the next tested version should be released next weekend. Translators please continue translating - I fixed lots of typos in the softare today hopefully without destroying any translations and updated the texts afterwards. 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] JOSM Tested
Hi Dirk, I have checked in a new Address Interpolation plugin into SVN - I hope it doesn't qualify as new since it doesn't change the JOSM code itself. Let me know if something doesn't look right. Thanks, Mike Nice -- From: Dirk Stöcker openstreet...@dstoecker.de Sent: Sunday, September 20, 2009 7:15 AM To: josm-dev@openstreetmap.org 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 the next tested version should be released next weekend. ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
[josm-dev] JOSM Tested
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@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM Tested
On Fri, Aug 14, 2009 at 11:31 PM, Dirk Stöckeropenstreet...@dstoecker.de 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 weeks, the cadastre-fr plugin is strongly disturbed by the ProgressMonitor dialog always on top, even with the preference window-handling.option-pane-always-on-to set to false. Pieren ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] JOSM Tested
2009/8/15 Pieren pier...@gmail.com: On Fri, Aug 14, 2009 at 11:31 PM, Dirk Stöckeropenstreet...@dstoecker.de 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 ? +1 the always on top worked much better some time ago, but don't know for the current stable. Now it happens that the detached properties-window (the tag-list) goes behind. It actually already started here: http://josm.openstreetmap.de/ticket/3109 That's really a blocker as you don't see the tags of selections anymore. If have to keep this window detached to see something: my screen resolution is too small (1000 vertical) to see anything if I don't (because you can't change the size of the docked windows cheers, Martin ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
