From Fedora Project Wiki
(Created page with "= Koji Generates Repositories of Signed RPMs = == Summary == Extend Koji with a new feature that allows users to generate yum repositories of signed RPMs. == Owner == * Name...")
 
Line 23: Line 23:
    
    
== Scope ==
== Scope ==
* Proposal owners:
* Proposal owners: Jay Greguske
<!-- What work do the feature owners 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?-->


* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: This feature does require coordination with release engineering (e.g. changes to installer image generation or update package delivery.
<!-- 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 -->
<!-- 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.
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.-->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
 
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- 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. -->
 
* Trademark approval: N/A (not needed for this Change)
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->


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

Revision as of 20:59, 9 November 2015

Koji Generates Repositories of Signed RPMs

Summary

Extend Koji with a new feature that allows users to generate yum repositories of signed RPMs.

Owner

  • Name: Jay Greguske
  • Email: jgregusk with the usual red hat domain
  • Release notes owner:

Current status

  • Targeted release: Fedora 24
  • Last updated: 2015-11-09
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

This is a significant enabler for generating DVD media, other ISOs, and images more efficiently. It also allows other tools such as mash or pungi to offload much of the heavy-lifting to the build system. Longer term, we may be able to reduce the number of tools needed to manufacture Fedora releases.

Benefit to Fedora

The benefit to Release Engineering should be self-evident: less tools, hosts, and services to maintain. This opens the door a little to let a small set of users generate their own signed repositories from Koji if they want to as well. This may be useful for QA testing.

Scope

  • Proposal owners: Jay Greguske
  • Release engineering: This feature does require coordination with release engineering (e.g. changes to installer image generation or update package delivery.

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

Documentation

N/A (not a System Wide Change)

Release Notes

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