Version numbering 1.2

Interesting article about the inconsistencies in version numbering conventions in open source software. I have heard a lot of marketing-speak about version numbering theories. Here are a few:
  • Version numbers shouldn't go too high, else it seems like the product has many problems that are fixed with every version. Microsoft marketing seems to think this way, Adobe doesnt.
  • Certain version numbers convey better software than others. Point-oh releases are a case in point, but odd numbers convey instability.
  • Your version numbers should be higher than your competitors' to signify a better product.
So obviously there is no panacea here. Personally, I would prefer version numbers to be an increasing sequence - for the lifetime of the product.

Comments

Post a Comment

Popular posts from this blog

Prolonging the battery life on your laptop/netbook running Ubuntu

mdz pointed me to Idea 24782 over at Ubuntu Brainstorm that urges the Ubuntu community to increase focus on making Ubuntu run longer on devices with batteries. I support the idea wholeheartedly. Since the advent of laptops and netbooks, users have wanted to stretch the battery to last that extra 15 minutes it'll require for them to finish up their email or their documents. In fact, the most popular idea ever on Brainstorm is about fixing suspend and hibernate. Unfortunately, it ended up becoming a whirlpool of several different ideas, albeit with a common theme - making the battery last longer . There are several things that can be done to make the battery on a mobile device last longer - some under user control, others under OS/firmware control and some others dependent on HW capabilities. I am going to attempt to summarize the various use profiles and what Ubuntu does (or can do) to prolong battery life in those profiles. Power management, when done right, should not requi
Read more

Touchscreen = fail?

Do you have a touchscreen that isn't working in Ubuntu? We need your help! We are trying to get as many touchscreens working as possible for Karmic. Bug #317094 is attempting to collect hardware information about these them. As a first step, we'd like to enable the ones that can use the in-kernel usbtouchscreen driver. Do you have a touchscreen? Is it connected over USB? ( lsusb is your friend) Get the vendor and product id of the USB touchscreen (lsub) Load the usbtouchscreen module and add the new id to it through sysfs A made-up example follows (I don't have a touchscreen handy, sorry!) example output from lsusb Bus 005 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader 0483 is the vendor id, 2016 is the product id sudo modprobe usbtouchscreen sudo sh -c "echo 0483 2016 > /sys/bus/usb/drivers/usbtouchscreen/new_id" Replace the vendor and product id with what you found from lsusb. If this makes your touchscreen work in Karmic, plea
Read more

Speeding up boot on an upgraded system

So I have a laptop that I've been upgrading since Hardy (currently on Karmic Alpha) that I would like to boot faster. It has probably accumulated a lot of crufty daemons along the way that probably aren't being pre-loaded into memory. I picked up this tidbit from the fast boot expert . Add profile to your kernel command-line (at the grub prompt, press Esc e and then edit the line) . This will update your system's readahead file list after a lot of disk churn. On my machine, it sped up boot by only about 5 seconds, but YMMV. Also, if you have a machine or netbook with SSD (flash) disks, sreadahead might give you a boost. Again, apt-get install sreadahread is your friend . sreadahead also schedules profiling of the system every month-or-so, so it keeps those boot-essential programs in the readahead cache always.
Read more