TestingLunarStable
Revision as of 11:05, 29 March 2012
Testing Lunar Stable
Introduction
Lunar has always been a bit of a bleeding edge distro, where some devs are keen to keep up-to-date with key packages as soon as new versions are released. However, while they may have successfully compiled and tested these packages on their own systems, there are some packages that require more extensive testing to make sure that they run on a wider range of systems, with different video or sound cards for example. In addition, while a major release of a package might add some important feature, it may take a couple of follow-up patch releases to iron out new problems which might have been introduced.
Users new to Lunar might experience problems if they install from the ISO and then update while such wrinkles are being sorted out. Therefore some of the Lunar developers would like to introduce "stable" and "unstable" versions of the Moonbase. The "stable" version would contain only modules that had been tested and approved by three developers, or where no obvious teething problems had been reported on the modules' mailing lists during the first month. New users would download modules from "stable" and developers would work with "unstable" to get the bleeding edge, just as before.
That's the theory. Now we have to set it up and see how it works in practice.
How to proceed
- Install from the ISO as usual
- lin moonbase
- lin theedge
- run lunar and make sure you select the stable branch, although it should be the default
- continue with a normal installation as described in man lfirsttime
- lin -cr gcc glibc gcc bash coreutil tar wget
- etc
You can report any problems via the Bug Tracker, the Lunar Mailing-List, or discuss them on the #Lunar IRC channel on Freenode.net
