From Fedora Project Wiki
 
Line 1: Line 1:
Let’s look at a couple of examples to make it (hopefully!) clear what we’re talking about.
+
{{admon/important|This page is deprecated| All Fedora Modularity Documentation has moved to the new [https://docs.pagure.org/modularity/ Fedora Modularity Documentation website] with source hosted along side the code in the [https://pagure.io/modularity Fedora Modularity website git repository]}}
 
 
=== Example 1: Our Atomic Host stack ===
 
 
 
We already release content that is organised in much this way, just not with any formal definition of modules or stacks.
 
 
 
Atomic, for example, is composed from multiple sources. Some content comes from traditional Fedora with its usual 6-month lifecycle; and some comes from -Extras with its much shorter lifecycle and rapid rebasing to pick up new features.
 
 
 
And even within Fedora we have different levels of lifecycle. An obvious example is Gnome; the Anaconda installer stack that we use for Atomic installer ISO images depends on this faster-moving content, even when the installed atomic host does not include it.
 
 
 
But even though these distinct sets of components all have differing lifecycles, they still belong within Fedora and we still produce coherent output images or artifacts from them today, with planned releases that require alignment between all the relevant parts. In the language of this document, it might look like this:
 
 
 
<!-- image 6 -->
 
[[File:building-image6.png]]
 

Latest revision as of 07:52, 20 February 2017

Important.png
This page is deprecated
All Fedora Modularity Documentation has moved to the new Fedora Modularity Documentation website with source hosted along side the code in the Fedora Modularity website git repository