From Fedora Project Wiki
Line 89: Line 89:
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


* Release engineering: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: Magically add SCLs builds into compose or set up koji for SCLs.
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here. -->


* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines:  
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
** https://fedorahosted.org/fpc/ticket/339
** https://fedoraproject.org/wiki/User:Toshio/SCL_Guidelines_%28draft%29


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==

Revision as of 22:24, 26 March 2014


SCL

Summary

SCL - Software Collections - are popular packaging format above rpm. Let's enable them for Fedora.

Owner

Current status

  • Targeted release: Fedora 21
  • Last updated: 26. 3. 2014
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

My first draft [1] is obsoleted by current state of SCL, Copr... I would keep the SCL workflow simple as possible.

Playground repo

1. Build SCL in Copr

2. Add SCL into Playground repo

Fedora main repo

0. Build SCL in Copr (or use existing SCL)

1. Do standard package review

2. Upload packages into git - specific branch based on Fedora version and name of collection. For stable repo we must be able to replicate builds from git repo, which Fedora own.

3. Build SCL in koji or magically add SCL builds from Copr (depends on preference of releng)

Benefit to Fedora

Cool programs depending on specific version of software can still run on Fedora. We see it often with Ruby (on Rails) projects like Puppet, Cloud projects (Katello, Foreman, OpenShift, OpenStack). All those cool apps can run on any Fedora, which will provide collection for them.

New versions of software can be also packaged as collection and tested it before inclusion into main Fedora repository in case the new version would seem to be to disruptive for rest of the system.

Scope

0. Approve SCL guidelines by FPC

1. Include at least one collection into Fedora Playground repository or into main Fedora repository (probably the one wanted by Cloud WG). It might be this one rebuild for Fedora http://copr.fedoraproject.org/coprs/rhscl/ruby193/. Updates of some gems or addition of other gems might be needed. Review by Cloud projects is needed.

  • Proposal owners: Marcela, ...
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: Magically add SCLs builds into compose or set up koji for SCLs.

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product <-- Applicable for Changes that blocks specific product release/Fedora.next -->

Documentation

N/A (not a System Wide Change)

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/SCL&oldid=374624"