Attachments (0)
Change History (7)
comment:1 by , 15 years ago
| Component: | Core → unspecified |
|---|
comment:2 by , 15 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:3 by , 15 years ago
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
| Summary: | Please do not link testing to totaly unstable version → Please do not link testing to unstable version |
follow-up: 5 comment:4 by , 15 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | reopened → closed |
We had a period of two weeks which was decidicated to bug fixing only. I think that is pretty much.
comment:5 by , 15 years ago
Replying to stoecker:
We had a period of two weeks which was decidicated to bug fixing only. I think that is pretty much.
Then please tell me why was version 2552 yesterday released as tested and unstable, if you were not able to open any .osm-file ?
Yes, sure it was a mistake but why was it unstable and tested at the same time ?
follow-up: 7 comment:6 by , 15 years ago
We had two issues in 2552. First was that english language did fallback into default language and second was, that plugin update failed on Windows systems due to illegal characters in filenames. Both are minor issues, but probably cause major errors on SOME systems. There has been no issue regarding opening osm files.
When we make a new version we consolidate the latest and when we think latest is stable enough we make it tested. This means at this time both are same. After a short grace period to fix bugs comming up due to the larger userbase (and resulting in a new tested) we start with next release cycle.
We don't make branches or other stable versions, as this is lots of work and about 30% of JOSM users anyway use latest. JOSM is designed as "works always". As this is not realistic, we have a tested, which is a state, where we think this is more stable than the most latest version.
comment:7 by , 15 years ago
Replying to stoecker:
We had two issues in 2552. First was that english language did fallback into default language and second was, that plugin update failed on Windows systems due to illegal characters in filenames. Both are minor issues, but probably cause major errors on SOME systems. There has been no issue regarding opening osm files.
Yes, I had: #4050
I do not have this problem anymore and version 2554 worked right away, so I do not know where it came from. Maybe it was my testing/unstable debian system.
Or some plugin ?
Sorry, I was a bit to hash and the days right before version 2552, I was offline and not testing.
When we make a new version we consolidate the latest and when we think latest is stable enough we make it tested. This means at this time both are same. After a short grace period to fix bugs comming up due to the larger userbase (and resulting in a new tested) we start with next release cycle.
Sounds goog for me
I do not think it is a good idea to release a version as tested if it is just new as unstable and not been tested.
Since version 2554 is from yesterday and there are already around 30 bugs could you please wait the next time maybe a week until releasing an unstable version as tested.
Thanks
Colliar