Testing Lunar Stable
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
There have been some blog posts and mails on the maillinglist, if you have been inactive for a while or if you are new, you might want to take a look at them:
- git pull
do work on stable branch you have to do the following once - In the folder you git-checkouted moonbase before
- git checkout -b stable origin/stable
to switch between branches
- git branch # lists all branches
- git checkout stable # switches to stable branch
- git checkout master # switches to unstable branch
- Be aware that unstaged changes are floating Which means if you edit a file and change branch that file will still be changed
- Always do git push origin master:master, that way you wont make the mistake of pushing stable to master if that branch is the active one
- When you want to transfer a working change from master you first run git checkout stable either you merge master into stable, or you run git cherry-pick shasum of the commit you want from master when happy you run git push origin stable:stable