مسیر سخت انتشار سنت او اس 8

رد هت اینترپرایز 8 در تاریخ  7 می 2019 منتشر شده است ، و همه منتظر هستند تا ساخت نسخه 8 CentOS تمام شود ، این صفحه برای پوشش مراحل انتشار جدیدترین نسخه CentOS در سال 2019 توسط من : مهران ، از رسانگار ایجاد شده تا ببنیم چه زمانی انتشار نسخه 8 نهایی خواهد شد ، این صفحه برای انشتار خط زمانی و پاسخ به سوالات عمومی در خصوص سنت او اس جدید نسخه 8 می باشد.

انتشار نسخه اصلی و بزرگ  CentOS نیاز به برنامه ریزی و تغییرات زیادی در ابزارها دارد ، چون این نسخه بر مبنای یک نسخه خیلی جدید تر از فدورا نسبت به نسخه قبلی می باشد

این یعنی همه چیز از جمله نصب کننده ، بسته های نرم افزاری ، نحوه بسته بندی و سیستم ساحت باید برای کار کردن با نسخه جدید سیستم عامل اورهال شود ، این یعنی همیشه یک بازه زمانی برای حمع بندی و اطمینان از علمرد لازم است تا یک نسخه کار کند ، تفاوت بین EL-7 و EL-8 هم مستثنی نیست ، چون کرنل به شدت تغییر کرده است ،

فرمت مخازن ماژول ها را اضافه کرده و RPM ها هم قابلیهای زیادی را شد داده اند به شکلی که قبلا در EL7 وجود نداشته. تنها چیزی که در این دوس نسخه تغییر شدیدی نداشته است ، سیستم init است که همچنان systemd خواهد ماند ،

این اولین بار است  EL5 با SysV, EL6 با Upstart, و EL7 با Systemd ارائه شده بودند

گامهای عمومی

Steps needed to make a CentOS rebuild usually follow these steps:

1. Red Hat makes the sources available.
   1. This used to be done via src.rpms but 7 changed to git repos
   2. In 8 CentOS has partnered closer with Fedora and will be sharing git repos with the Fedora system
   3. The pushes from Red Hat started on 2019-05-07 and ended 2019-05-08
2. CentOS needs to look at the sources and determine what is needed to build these packages
   1. The rpm format has added items like Suggests which change some tooling requirements
   2. The packaging format has moved from yum to dnf4/yum4 which added modularity. Modules are an additional hurdle because they allow parallel available versions of software but not parallel installability (aka you can build perl-5.24 and perl-5.26 and all perl modules need to be compiled against both sets.) Module stream versions are tied to certain timestamps which means you can’t rebuild the RHEL or Fedora and get the exact same version name.
   3. There are always packaging loops which need to be worked out. You need golang-(X-1) to build golang-X but golang-(X-1) doesn’t exist yet.. how do you build a version and break the loop?
3. CentOS needs to set up a build system which can allow for these changes.
   1. While CentOS can use the Fedora build system as a template, there are items in it which don’t make sense for CentOS.
   2. The EL-8 beta was useful but there are still major changes which need rethinking
4. CentOS needs to go through the source code and find out all the places where debranding is needed.
   1. No you can’t just “sed s’/Red Hat/CentOS/’ (someone always offers that)
   2. There are times when you do replace and times when you don’t.
5. Builds can start occurring through the system
   1. This usually requires a multi-loop as you do a build to get started
   2. Then rebuild that core with itself

   3. Then add some more and possibly repeat 1 && 2 a couple of times.

   4. Then you can start building out the rest of the packages
6. The installer usually takes a certain amount of work to get packaged together.
   1. Some things need additional patches
   2. Some things just need to be ordered correctly
   3. Some things like shim signatures for Secure Boot take outside review by signing authority
7. QA work can begin
   1. with testing of packages by themselves or building from them
   2. with installer testing for smoke tests
8. Usually some sort of RC work is done
9. نسخه نهایی منشتر شده است

The above is a ‘you asked the people trying to build the train when it will arrive’ guide. That said, every release is different and the order and additional steps get found and added each time.

وضعیت کلی سنت او اس 8

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.

معماری CentOS 8

معماری اصلی

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

جدول زمان بندی فعلی

بروز رسانی جدید

• 2019-07-26 The work on getting images and builds in place are ongoing. Packages have been built and the work on getting the installer integrated with the code is ongoing.

تعاریف

• DONE -فرایند کامل شده است 
• Ongoing – کارها در دست اقدام است 
• Not started – این گام به این معنی است که یا باید کاری از گام دیگر کامل شده و یا شخصی مشخص که در حال کار روی مرحله دیگری است برای آن زمان اختصاصی بدهد.