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

Karl Guggisberg karl.guggisberg at guggis.ch
Mon Mar 8 12:56:03 GMT 2010


Hi Colliar

Yes, you're right, that's how how most professionals in most other 
commercial and OS projects work,
or at least try to work. Unfortunately, JOSM is different. The JOSM 
release process is one of the
many JOSMisms which are often hard to understand for both JOSM users and 
JOSM contributors.

Please forget about the "r-2010-01-blocker"s. They've been introduced in 
an attempt to prepare and
stabilize a release when the current "maintainer" handed over 
responsibility  to two of us, because he didn't have time.
Just ignore them. The current "maintainer" is apparently back in business.

Actually, "two of us" is wrong. bastik took over responsibility and did 
most of the work for the last "tested" build, thanks!

Regards
Karl

Am 08.03.2010 12:33, schrieb colliar:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hi
>
> Thanks a lot for your work.
>
> 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.
>
> I also find 5 bugs left with keyword: "r-2010-01-blocker". Are you planning to
> solve them before working on upstream ?
>
> I think tested should be a version without any blocker/critical bug reported on
> and being tested as unstable/latest for a week.
>
> cu co
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEAREIAAYFAkuU4HQACgkQalWTFLzqsCvMywCgs8SAs189fgYDMY+gekkB0dB9
> TaQAn2mUVrBjnhUcp65UukpXrA2YvCCz
> =5hlO
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> josm-dev mailing list
> josm-dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/josm-dev
>
>    




More information about the josm-dev mailing list