Difference between revisions of "FLOP:Release Engineering"
m (Daniel Robbins moved page Funtoo Linux Release Engineering Proposal to FLOP:Funtoo Linux Release Engineering Proposal)
|Line 1:||Line 1:|
'''Jonathan Vasquez (fearedbliss)'''
'''Jonathan Vasquez (fearedbliss)'''
|Line 262:||Line 267:|
Revision as of 21:24, February 23, 2014
Funtoo Linux Optimization Proposal: Release Engineering
Jonathan Vasquez (fearedbliss)
This is a proposal to implement a strong release engineering infrastructure for Funtoo Linux. Funtoo currently is _only_ a rolling-release distro and does not have the _option_ to also be non-rolling. In order to create a more stable Funtoo system, this proposal will be offering a few things that we can do to make that happen.
The below proposals will not change Funtoo from a rolling-release system to a non-rolling release system. It will simply add the option to be non-rolling. Funtoo will also not be a binary distro. It will still be a source based distro but it will also have the ability to use binaries for a few select packages (Basically the Gentoo Reference Platform will be restarted and improved).
I believe that this will also make running Funtoo for users that want further stability and/or users that are running Funtoo as a server in an enterprise environment/or otherwise, more feasible.
The following things are proposed:
- Semi-rolling release model for Funtoo-RELEASE and Funtoo-STABLE (Funtoo-CURRENT will stay rolling release)
- A Complete Core OS
- A set of monitored applications that will be checked for stability and consistency
Semi-rolling Time Based Releases
The semi-rolling release model is a hybrid between a rolling release and just a regular release. This means that instead of bring new packages in all the time (rolling release), and instead of just completely freezing everything and bringing new packages/features every X months, we can have a middle ground where we can branch the Funtoo-CURRENT git branch and then focus on stabilizing that tree. Once we stabilize it, people can use it without having to worry about major version upgrades. The user can then use this branch until another branch later in the future is created. The user can then easily upgrade to the new branch by switching their SYNC variable.
So essentially it is a slow rolling-release (or semi-rolling or rolling-release with speed bumps).
Names for Funtoo's 3 git branches:
- Funtoo-CURRENT (Latest Developments - HEAD. This is the normal funtoo-current tree.)
- Funtoo-RELEASE (Just a release in a specific point in time - a branch of Funtoo-CURRENT is created, frozen, and stabilize.)
- Funtoo-STABLE (This is the same as a RELEASE but it is supported for a longer period of time).
Which branch is for what person?
The Funtoo-CURRENT branch is for people who want to be on the bleeding edge all the time. You will get the latest updates, and here is where all the development happens. Your system might not be fully stable all the time, and things might fail to compile. This is literally the traditional Gentoo rolling-release model. If you are used to using Gentoo/Funtoo, and want to continue using your system the way it has always been, this is the branch for you.
The Funtoo-RELEASE branch is for people who want to be rolling and receive new features but be more stable than Funtoo-CURRENT by using a frozen portage tree at a specific point in time that is audited for stability.
The Funtoo-STABLE branch is for people who prefer stability and don't need the latest features that are in the RELEASE branches. This branch is frozen for a longer period of time.
Example of 4 month RELEASE cycle, and a 2 year STABLE cycle
For the branch developments: Let's picture a 4 month RELEASE cycle (semi-rolling), and a 2 years STABLE cycle. If we expand this starting from January 2013, we would get the following releases over two years:
Funtoo-13.1-STABLE (January 2013) Funtoo-13.2-RELEASE (May 2013) Funtoo-13.3-RELEASE (September 2013) Funtoo-14.1-RELEASE (January 2014) Funtoo-14.2-RELEASE (May 2014) Funtoo-14.3-RELEASE (September 2014) Funtoo-15.1-STABLE (January 2015)
This gives you 2 STABLE releases in two years and 5 RELEASEs in between. That's a total of 7 releases. STABLE releases only get bugfixes and security updates. RELEASE are for people that want to get the latest bleeding edge stuff, but still want to be stable within RELEASEs.
For people that are used to the normal Gentoo/Funtoo stuff, you could just stay on the Funtoo-CURRENT branch.
Example of 3 month RELEASE cycle, and a 2 year STABLE cycle
Funtoo-13.1-STABLE (January 2013) Funtoo-13.2-RELEASE (April 2013) Funtoo-13.3-RELEASE (July 2013) Funtoo-13.4-RELEASE (October 2013) Funtoo-14.1-RELEASE (January 2014) Funtoo-14.2-RELEASE (April 2014) Funtoo-14.3-RELEASE (July 2014) Funtoo-14.4-RELEASE (October 2014) Funtoo-15.1-STABLE (January 2015)
If we have have a 3 month (semi-rolling) cycle, we would end up with 2 STABLE releases and 7 RELEASEs within two years. This is a total of 9 releases.
What will these branches contain? What will they focus on?
Funtoo-RELEASE and Funtoo-STABLE branches will only focus on the stability of specific packages that we are deciding to maintain at a specific point in time. All outside packages can be installed and maintained by outside package mantainers.
A Complete Core OS
An operating system is not just a stage3 tarball. The stage3 will not boot by itself, but rather needs the user to compile a kernel and install a bootloader. We should have a well tested default kernel that is tested for stability. This will speed up deployments and will provide predictability for kernel modules, and other applications that rely on a kernel. We will also need to provide a way for the system to boot this kernel. Thus a default bootloader should be provided.
- stage3 (Minimal @system applications needed for a functional Funtoo base system)
- kernel (bliss-kernel can become the base of funtoo-kernel - or another kernel you think is good)
- bootloader (a default bootloader to provide a seamless, fast, and easy deployment experience)
Monitored Set of Applications
In order for us to make a release stable, we will need to monitor a set of applications that we believe are essential for people that want to install servers and desktops. All of the monitored applications should work fine, they should be able to compile with no bugs (If the user is compiling), and they will also have binaries available. (The binaries will be compiled with the default and recommended USE flags that Funtoo developers believe give a functional binary).
Proposed set of packages:
- Critical packages of stage3 that provide the Funtoo base system.
|Chrome Plugins for Chromium||www-plugins/chrome-binary-plugins|
|Google Talk Plugin||www-plugins/google-talkplugin|
|Adobe Flash Player||www-plugins/adobe-flash|
Command Line & Tools Applications:
Of course this is just a list of applications that I've deemed important for server and desktop users. More applications should be added so that we can filter mostly used and important applications, from other more fringe applications.
/etc/gentoo-release -> /etc/funtoo-release (rename this file)
should contain information for the currently installed release:
Funtoo-13.1-STABLE (January 2013) Funtoo-13.2-RELEASE (May 2013) Funtoo-13.3-RELEASE (September 2013) Funtoo-14.1-RELEASE (January 2014) Funtoo-14.2-RELEASE (May 2014) Funtoo-14.3-RELEASE (September 2014) Funtoo-15.1-STABLE (January 2015)blog comments powered by Disqus