On Thu, Feb 3, 2011 at 11:20 AM, Adam Bark <adam.jt...@gmail.com> wrote: > > I figure the code is 0.10.10 so until it hits 1.x I won't assume > anything. As for Favux's comment you don't have to update immediately > it's only just been checked in so won't be in a release for a little while. >
Assuming 0.x will have unstable interfaces is great, but I've noticed some projects retain a vestigal "0." prefix for several years, despite being mostly stable (VLC is the poster-child for this, taking 13 years to hit 1.0). I'm new to the list (joined a few days ago) so I don't really know the project history or roadmap very well, but if the point releases are any indication of interface stability, then "major changes" happen about every two years. That's pretty stable, despite its 0.x status. On Thu, Feb 3, 2011 at 1:54 PM, Peter Hutterer <peter.hutte...@who-t.net> wrote: > would something like: > xsetwacom get <device name> RelWUp > "RelWUp is obsolete. Please use RelWheelUp instead" This seems like the best solution to me. I'm all for making things more readable, but we shouldn't suddenly pull the carpet out from the people who have been using the existing xsetwacom interface for literally years... Jason ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
