On Wed, 18 Jan 2012, colliar wrote:
Am 26.12.2011 18:18, schrieb David Paleino:
"Stable" doesn't -- generally speaking -- accept new versions of packages. The
only way josm could be upgraded in stable is when OSM changes API to 0.7 (or it
becomes otherwise unusable). Also then, the preferred "form of upgrade" would
be a minimal patch to support the new API -- so no new JOSM, really ;) (hey,
it's called "stable" for a reason).
This is true for the surroundings + dependencies but defenitly not for
JOSM itself !
You might have a testing and a unstable version but no stable in the
sence of debian.
Personally, I would advice everyone to not use r33..
Debians stable policy is based on the wrong assumtion, that for stable the
bugs are fixed and no features are added. But as for most packages
bug-fixes aren't done, the "debian stable" simply is a "debian old".
They should rename it from unstable, testing, stable to new, old and very
old.
JOSM 3376 is not more or less stable than an other tested (only fact is
that it requires an 5 and not an 7 year old Java version).
Whereas old Java version actually are unstable, as JOSM triggers a lot of
Java bugs fixed in newer versions.
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
_______________________________________________
josm-dev mailing list
josm-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/josm-dev
