Search results

= Using the bodhi command-line interface = == Installing the client ==

...cker Hub. This change proposes that Fedora infrastructure is used to build the container instead. * Targeted release: 24

= Annobin Used By Bodhi = ...analysis of the security hardening of a compiled package when reviewing a Bodhi update.

Extend Koji with a new feature that allows users to generate yum repositories of signed RPMs. * Email: jgregusk with the usual red hat domain

Stop producing and distributing the Modular and Everything i686 repositories. * Targeted release: [[Releases/31| Fedora 31 ]]

...on out karma points for testing updates that you have currently installed. The typical workflow is as follows: ...r directly run fedora-easy-karma and test packages according to the update notes

...itted to a fedora-updates repository should not be automatically pushed to the stable repository when its karma threshold is reached. ...to be performed by different people from different teams. Please look at the ''Intermediate milestones'' section below.

The GHC Haskell compiler will be updated from major version 8.8 to 8.10, and Haskell packages will be updated from Stackage LTS 16 to LTS 18 versions.

= Additional buildroot to test x86-64 micro-architecture update = Create a dedicated buildroot to test packages built with x86-64 micro-architecture update.

...ntly targets end-users, however, this document may be updated periodically to target everyone. = What is Bodhi =

Note: meeting notes aren't regularly updated. ...org/wiki/ReleaseEngineering/ReleaseToolsMattDMPriorityNotes Matthew Miller notes] (representing RHEL, Council, etc)

...table rawhide as well as less work on the infrastructure and rel-eng teams to keep composes working. ...in two phases, at first only single package updates will be supported, in a second stage, we will add support for multi-packages updates.

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> The GHC Haskell compiler will be updated from major version 8.6 to 8.8,

...table rawhide as well as less work on the infrastructure and rel-eng teams to keep composes working. ..., owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

= Make Fedora CoreOS a Fedora Edition = This change is to promote Fedora CoreOS to Edition status alongside Cloud, IoT, Server and Workstation.

...he Fedora brand, and if we want to see Fedora in use on the cloud, we need to step in and take responsibility for Fedora. ...: a process that creates Fedora EC2 images as a part of the regular Fedora release process, starting with Fedora 13.

Use this guide to determine to which category your proposed change belongs to. ...nges to isolated/leaf package without the impact on other packages/rest of the distribution

...systems to createrepo_c 1.0 and change repositories metadata settings <!-- The name of your change proposal --> = ...move all following releases to the new settings, while preserving most of the current settings for releases <= 40.

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> = rpmautospec - removing release and changelog fields from spec files =

Use this guide to determine to which category your proposed change belongs to. ...nges to isolated/leaf package without the impact on other packages/rest of the distribution