m (→Dependencies) |
mNo edit summary |
||
| Line 143: | Line 143: | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: | * Contingency mechanism: Cancel release of the Modular Server Beta; decision to be made by Modularity WG, Factory-2, & BRT Leads. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: | * Contingency deadline: Beta Freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
** To lower disruption to other Fedora Editions we may want to intentionally delay this release to have "Deadline+1-week" for the complete F26 schedule | |||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? | * Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* Blocks product? | * Blocks product? No <!-- Applicable for Changes that blocks specific product release/Fedora.next --> | ||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |||
* [[Modularity]] | |||
== Release Notes == | == Release Notes == | ||
| Line 162: | Line 163: | ||
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | ||
--> | --> | ||
* Content to come | |||
[[Category:ChangePageIncomplete]] | [[Category:ChangePageIncomplete]] | ||
Revision as of 01:27, 11 January 2017
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
INCOMPLETE, DO NOT REVIEW
Changes/Modular_Server_Beta
Summary
As we progress down the modularity path, we finally have enough content, architecture and understanding that we would like to release an edition of Fedora that is actually usable. However, as we aren't ready for production yet, we would like to do a "beta" release so that people can see it and try it but it doesn't actually take the place of a production edition. As such this Change Proposal requests that we set up a "Modular Server Edition" with some sort of flag that indicates that it is meant for experimentation and not real use. We plan to model the Server Edition in content and most use scenarios.
Owner
- Name: Langdon White
- Email: langdon@fedoraproject.org
- Release notes owner:
- ?? FESCo shepherd: Shehperd name <email address>
- Edition: N/A but in collaboration with Server WG
- Responsible WG: Modularity WG
Current status
- Targeted release: Fedora 26
- Last updated: 2017-01-11
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
The modularity effort is fairly well known and significantly more information may be found on the wiki or the YouTube Channel. In short, modularity is attempting to disconnect the lifecycle of applications from 1) each other 2) the operating system while still maintaining the ease of use of a typical Linux Distro.
Benefit to Fedora
Scoping the question to this Change Proposal, the benefit to Fedora is 2-fold. First, distributing an early version of a usable example of Modularity will allow for feedback and exposure to a wider audience than the people closely following the project. Second, we will be able to exercise the release processes we have been changing to support Modularity and improve the Fedora Infrastructure.
Scope
- Proposal owners:
- The Modularity WG, Factory 2.0, Base Runtime, and Server WG teams all have contributions to this effort. The work that each team is doing is significant and wide ranging. However, as the release is being managed in a "beta channel" none of the changes, whether released on time or not, will impact any other aspect of Fedora. Also, while we have high hopes for the amount of content we plan to release, even a small percentage of that content being ready will be enough to help prove the concept and generate feedback.
- Other developers:
- We would like to enable Fedora Packagers to provide modules to this release of Modular Server.
- We would further like to provide the ability for Fedora Packagers to provide containerized variants of their packages/modules
- Release engineering:
- List of deliverables: Numerous but largely aligned with the Server WG Logic Model
- Release engineering needs to create and deliver this new "edition." The Factory 2 team is largely responsible. Ralph has been the primary point of contact thus far.
- A beta edition delivering the Modular Server
- Policies and guidelines:
- New guidelines[[[Fedora_Packaging_Guidelines_for_Modules|1]]][[[Container:Guidelines|2]]] are required, they are in beta state like the rest of this proposal.
- New guidelinesFedora_Packaging_Guidelines_for_ModulesContainer:Guidelines are required, they are in beta state like the rest of this proposal.
- At this point there are no changes expected to existing guidelines
- Trademark approval: N/A (not needed for this Change)
- This is based on a Fedora Objective and, as a result, does not seem to require Trademark approval even though it will carry the Trademark
Upgrade/compatibility impact
Arguably, this is not applicable as the delivery is for a beta version of an Edition. We do expect to have an upgrade path but it will be as risky as anything else in the beta.
How To Test
Normal system operation (sort of). We are delivering this Beta in order to get exactly this sort of feedback. We would like to hear from anyone experimenting with the beta about how it does or does not meet their expectations.
Feedback channel is not well determined. The team requests that the Change Wrangler make recommendations. Bugzilla is probably not appropriate but fedora-devel, modularity-wg pagure issues, modularity-wg meetings would all be viable choices.
User Experience
See above.
Dependencies
Although a System Wide Change, not applicable.
Contingency Plan
- Contingency mechanism: Cancel release of the Modular Server Beta; decision to be made by Modularity WG, Factory-2, & BRT Leads.
- Contingency deadline: Beta Freeze
- To lower disruption to other Fedora Editions we may want to intentionally delay this release to have "Deadline+1-week" for the complete F26 schedule
- Blocks release? No
- Blocks product? No
Documentation
Release Notes
- Content to come