Il giorno dom, 18/05/2008 alle 18.15 +0200, Torsten Werner ha scritto: > I do not think that the bug is valid. Requiring that josm/stable stays > compatible with future OSM-API versions is like requiring that > linux-image-*/stable and xorg/stable stays compatible with future > hardware. BTS, there is always a slight chance to get an updated > version of josm into a stable point release.
I don't agree: an out-of-date linux or xorg continues to work well on most of the cases (just a few people have new and unsupported hardware), while an out-of-date josm wouldn't work for anyone. I'd love very much to close this bug, but I don't think it would be wise to do it. What would be the slight possibility you're talking about? Do you think we have enough probability that Release Managers let an update of an unknown package like josm enter an already released stable? IANADD, so I can't do other than trust you, if you say that, but I'm quite skeptical about this possibility. :-) Regards, Giovanni. -- Giovanni Mascellani <[EMAIL PROTECTED]> Pisa, Italy Web: http://giomasce.altervista.org SIP: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] / [EMAIL PROTECTED] GPG: 0x5F1FBF70 (FP: 1EB6 3D43 E201 4DDF 67BD 003F FCB0 BB5C 5F1F BF70)
Description: Questa è una parte del messaggio firmata digitalmente
_______________________________________________ Pkg-grass-devel mailing list Pkgemail@example.com http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel