Revision as of 13:00, 4 January 2017

Changes/BaseRuntime

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

Targeted release: Fedora 26
Last updated: 2017-01-04
Tracker bug: <will be assigned by the Wrangler>

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.

Release engineering: Release engineering, Fedora Infrastructure and Factory 2.0 will enable the modules dist-git namespace and deploy the Module Build Service into production. This will be done as part of a separate change.
- List of deliverables: N/A

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

TBD.

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

@@ Line 53: / Line 53: @@
 == How To Test ==
-<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
+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.
-Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
-A good "how to test" should answer these four questions:
-. What special hardware / data / etc. is needed (if any)?
-. How do I prepare my system to test this change? What packages
-need to be installed, config files edited, etc.?
-. What specific actions do I perform to check that the change is
-working like it's supposed to?
-. What are the expected results of those actions?
--->
-TBD.
 == User Experience ==

Search

Changes/BaseRuntime: Difference between revisions