CentOS 8.x Rough Status Page

Red Hat Enterprise Linux regularly releases 'point' releases which contain rebases and changes in code. When this happens, there is usually a noticeble lag between when they start appearing in CentOS. This is due to the steps needed to get builds working which is similar to getting the .0 build in place.

General Steps

The following are high level steps which change slightly depending on the release. Early X.1 -> X.5 releases tend to have much more little work which can delay moving from place to place in the chain. Later X.Y releases usually move faster as the changes to anaconda or other places are smaller.

1. Red Hat makes the sources available via git.centos.org

The process for this is fairly automated but problems do occur. CentOS and Red Hat engineers check to see that all code was pushed out. Some code may have gotten 'stuck' so a repush is needed.

2. CentOS engineers start checking the code to see what changed between X.Y and X.Y+1

Certain packages need more work like rpm which may trigger larger rebuilds. Packages may have large rebases between what was in the previous point release. These may bring in new packaging loops. Some packages may need some build dependency which wasn't shipped. Zhese need to be worked out.

3. Rebuilds of package chains begin

4. Modular rebuilds need to happen which may fail and need rebuilds.

5. Review of trademark changes and previous CentOS patches need to be seen if they are still needed.

6. Work on whatever changes/fixes in the installer and tool progresses.

7. Packages can get the first QA team testing. Packages which fail need to go back to 2.

8. Packages are then pushed to the CR repository so people willing to take the plunge can test. Problems here are rare but can occur and we go back to 2 for those packages.

9. Finish work on installers and see if DVD, containers and other artifacts can be built.

10. A new snapshot compose of CentOS-X.Y+1 is created and staged on the CentOS CDN.

11. Symbolic links change and file permissions are changed.

12. CentOS-X.Y is moved to vault.centos.org

Current Build Status

In the above roadmap, we are currently somewhere in the middle of step 5 but as part of that, still finding things to fix up for step 4.

The current status of all builds can be seen on CentOS Linux 8 Builder Packages that have failed to build (patches are welcome, send to the centos-devel mailing list) can be seen on Failed Builds

Architectures

Main architectures

The following arches are built automatically in parallel in our new Build System :

x86_64 (w/ i686 multilib)

ppc64le (Little Endian)

aarch64 (ARM64, ARMv8)

Responsibility, Owner: CentOS Core SIG

AltArch

The following architecture (not existing upstream, so more difficult to boostrap) is also actually being worked, on, but mainly based on a combination of Fedora 27/28 pkgs that can be used to bootstrap the el8 beta rebuild and then iterating loops until we can include that architecture in our Koji Build System. Update: bootstrap phase is done, so now you can follow builds on Armhfp Build System

armhfp (ARM32, ARMv7 - aka armv7hl)

Responsibility, Owner : CentOS SIG-AltArch

Current Timeline 8.2.2004

Item Started Ended Status Sources pushed to CentOS Git 2020-04-28 2020-04-28 DONE Source code evaluation 2020-04-28 2020-05-05 DONE Build Packages 2020-04-29 2020-05-04 DONE Installer work 2019-05-04 2020-05-18 DONE QA work 2020-04-29 2020-06-15 DONE CR work 2020-0?-?? 2019-0?-?? N/A Release work 2020-06-10 2020-06-15 DONE Final release 2020-06-15 2020-06-15 DONE

Timeline for 8.1.1911