From Fedora Project Wiki

< Changes

Revision as of 13:48, 28 July 2017 by Pbrobinson (talk | contribs) (→‎Scope)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Base Runtime

Summary

We will deliver the first release of Base Runtime, a module providing base operating system features that application level modules can build and depend on. This module will be the foundation of the new modular Fedora 26 Server release.

Owner

  • Name: Petr Šabata
  • Email: contyk@redhat.com
  • Release notes owner:
  • Responsible WG: Modularity

Current status

Detailed Description

See the Base Runtime Fedora 26 MVP document for details.

Benefit to Fedora

See the Base Runtime and Modularity pages for argument.

Scope

  • Proposal owners: The Base Runtime team will prepare the Base Runtime module and its build environment as both the module metadata recipes in the modulemd format and the built binary RPM artifacts.
  • Other developers: No extra work besides cooperation with resolving potential package FTBFS issues or assisting the team with the minimization effort is necessary.
  • Policies and guidelines: No new policies or guidelines will be prepared for the Fedora 26 deliverable. General module packaging guidelines will be created for Fedora 27 or later, as the infrastructure becomes generally available.
  • Trademark approval: ?

Upgrade/compatibility impact

This is the first modular release of the base system and will be available as a technology preview and an alternative to the traditional release. Only new, clean installations will be supported.

No package or module level updates will be available for this release.

How To Test

If a modular compose of Base Runtime is available, installable and bootable, either as part of the modular Server release or standalone, it's a success.

User Experience

Installed modular products shouldn't significantly differ from their non-modular counterparts. However, since the content will be built separately in standalone buildroots and may include different package versions in some specific cases, 100% compatibility cannot be guaranteed.

No updates for the modular content will be issued during the Fedora 26 timeframe as the update instructure doesn't yet support this feature.

Dependencies

Since Base Runtime will be delivered as a module, a working instance of Module Build Service needs to be available in the production Fedora infrastructure environment.

Contingency Plan

  • Contingency mechanism: N/A
  • Contingency deadline: N/A
  • Blocks release? No
  • Blocks product? The modular release of Fedora 26 Server

Documentation

See the Base Runtime page for details.

Release Notes