Goals of Archlinux-Stable
We will strive to provide a stable branch for Archlinux. This project shall serve to compliment and benefit Arch, the rolling release, and the community by conforming to The Arch Way and the K.I.S.S principle.
Our Development Cycle
At the beginning of a cycle, we take a snapshot of the PKGBUILDs from Archlinux Official. From here we enter a short period of open-version development. During this period, we examine the most important packages in the base system. We then decide if the versions of these packages have sufficient features, stability, and supportability. We welcome suggestions on package versions/feature requests during this period of our cycle. The next period of our development cycle is a version freeze. The existing major versions and features of packages are "locked in" at this point. Any development to the system is in the form of patch fixes for bugs and security. After sufficient testing and bug discovery, this period is closed. The final segment in our development cycle is the release period. Our packages will be published and made available to the public for installation and usage. This is considered as "the release". While "the release" is current, we will continue to monitor the packages for security and bug fixes. When a new patch is implemented, it will be made available through the Archlinux package manager's update mechanism. During this period, a new development cycle should be simultaneously started in the first period. The simultaneous start will be in open-version selection stage while we maintain patches for "the release".