I wonder if out release number is confusing. It certainly seems quite unique to me and I can understand why external groups may not follow it.
Would we do better to move away from the odd/even scheme and immediatly after a release 0.24 go to for release 0.25 milestone 1, then 2, 3 etc... then alpha then beta then stable release release 0.25. I guess the licence for MDR may be a problem for some. I think I'd prefer that they didn't ship ArgoUML at all than ship such an old version. Bob. On 11/01/07, Tom Morris <[EMAIL PROTECTED]> wrote:
Hans Nordhaug mentioned the Debian and FreeBSD redistributions of ArgoUML. I discovered JPackage distributes an ArgoUML rpm. I'm sure there are other distributions hiding. Here's where they are in terms of ArgoUML versions: FreeBSD 0.22 http://www.freshports.org/devel/argouml/ Debian 0.19.6 http://packages.debian.org/unstable/misc/argouml JPackage rpm 0.17.5 http://www.jpackage.org/browser/rpm.php?jppversion=1.6&id=2090 FreeBSD gets a gold star for only distributing stable releases and for staying current from 0.12 all the way through 0.22 which they just incorporated a few weeks ago. The others seem to distribute in an ad hoc fashion (eg Jpackage: 17.1, 15.4, 14.3) and distribute develop releases as often as stable releases. Do we care? Should we encourage distribution of stable releases? Discourage distribution of unstable releases? Give up because it's too hard to affect any meaningful change? It's nice to have more people exposed to the tool, but not if they have a terrible first experience. The change in dependencies between 0.18.1 and 0.20 (MDR vs NSUML) may be part of the reason that some folks are stuck on older releases, but that's just a guess. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
