Pbrobinson (talk | contribs) m (→Scope) |
|||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
= | = Base Runtime = | ||
== Summary == | == Summary == | ||
| Line 24: | Line 24: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1413528 #1413528] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 80: | Line 80: | ||
--> | --> | ||
[[Category: | [[Category:ChangeAcceptedF26]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
| Line 87: | Line 87: | ||
<!-- Select proper category, default is Self Contained Change --> | <!-- Select proper category, default is Self Contained Change --> | ||
[[Category:SelfContainedChange]] | |||
<!-- [[Category:SystemWideChange]] --> | <!-- [[Category:SystemWideChange]] --> | ||
Latest revision as of 13:48, 28 July 2017
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.
- 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
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.