From Fedora Project Wiki
9 September 2016
- 14:0614:06, 9 September 2016 diff hist +18 m Modularity/Architecture/Infra →Infrastructure TOC
- 14:0514:05, 9 September 2016 diff hist +10 m Modularity/Architecture/Infra →See also
- 14:0414:04, 9 September 2016 diff hist +43 m Modularity/Architecture/Module versioning and branching No edit summary
- 14:0214:02, 9 September 2016 diff hist −25,146 Modularity/Architecture/Module versioning and branching No edit summary
- 14:0214:02, 9 September 2016 diff hist 0 m Modularity/Architecture/Module versioning and branching →Summary
- 14:0114:01, 9 September 2016 diff hist +1 m Modularity/Architecture/Module versioning and branching/Constrains on branching No edit summary
- 14:0014:00, 9 September 2016 diff hist +3,077 N Modularity/Architecture/Module versioning and branching/Constrains on branching Created page with "The above seems to say “branching is hard, let’s not assume what it looks like but just store a flexible representation that we can adapt as we need.” That’s true to ..."
- 13:5913:59, 9 September 2016 diff hist +6,672 N Modularity/Architecture/Module versioning and branching/Managing this branching complexity Created page with "Given that the exact and branching policy for a module is currently inconsistent between products, needs to remain flexible, and changes over time, how do we manage this? The ..."
- 13:5813:58, 9 September 2016 diff hist +9,424 N Modularity/Architecture/Module versioning and branching/Coherency of branching Created page with "There are many advantages to be had in a single, coherent view of the branching structure for a given module. Maintainers and customers alike have to deal with branches in mu..."
- 13:5713:57, 9 September 2016 diff hist +3,707 N Modularity/Architecture/Module versioning and branching/Properties of branches and update streams Created page with " '''ABI Compatibility: '''Updates within a single update stream are likely to maintain ABI backwards compatibility in most cases. Users should be able to consume updates from ..."
- 13:5613:56, 9 September 2016 diff hist +2,069 N Modularity/Architecture/Module versioning and branching/Basic branching terminology Created page with "First, though, note that the very word “version” is overloaded here. It can refer either to a completely separate branch of some module, or to a single specific instance o..."
- 13:5413:54, 9 September 2016 diff hist +616 m Modularity/Architecture/Module versioning and branching →Summary
- 13:3213:32, 9 September 2016 diff hist +8 m Modularity/Architecture/Module versioning and branching No edit summary
- 13:2813:28, 9 September 2016 diff hist +98 Modularity/Architecture/Infra/Infrastructure services proposal No edit summary
- 13:1113:11, 9 September 2016 diff hist +47 m Modularity/Architecture/Infra No edit summary
- 13:0913:09, 9 September 2016 diff hist −30 m Modularity/Architecture/Infra No edit summary
- 13:0913:09, 9 September 2016 diff hist −17,483 Modularity/Architecture/Infra No edit summary
- 13:0613:06, 9 September 2016 diff hist +3,870 N Modularity/Architecture/Infra/Open questions and notes Created page with "= Open Questions = As mentioned before, we have an open question about how to '''uniquely identify components''' and modules. That’s outside the scope of this document, bu..."
- 13:0513:05, 9 September 2016 diff hist +2,564 N Modularity/Architecture/Infra/Two approaches to the orchestrator Created page with "== Two Approaches to the Orchestrator == In the Modularity Group, we have two approaches to take in how the orchestrator and koji relate to each other. They differ in which ..."
- 13:0413:04, 9 September 2016 diff hist +7,951 N Modularity/Architecture/Infra/Infrastructure services proposal Created page with "Here is an overview diagram of the set of systems and services that would be involved in maintaining, building, and shipping a module. 800px ..."