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

...[http://pl.linkedin.com/in/dmierzej professional system engineer]. I like to keep things neat and tidy, so whenever I come across some software that I ( The list of packages maintained by me can be found [https://src.fedoraproject.o

...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

...the standard format and templates improves the readability and quality of the pages. ...ugs'' keyword for the bug, and add a link to the Common Bugs page entry to the bug's ''Whiteboard'' field.

...probar/testar los paquetes acorde con las notas de actualización. (updates notes) You will be asked for every package installed from updates-testing to provide

Update the PHP stack in Fedora to the latest version 8.2.x ..., 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.

Ongoing prioritization for release tools work from Matt Miller via bi-weekly sync. ...conversations with OpenShift team about deploying an OpenShift instance in the Fedora space & having more participation

Add the [https://github.com/juhp/fbrnch fbrnch] packager tool to Fedora. ...to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->

...er from major version 9.4 to 9.6 and Haskell packages from Stackage LTS 21 to LTS 22 versions. ..., 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.

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> This change is to enable package maintainers to build Flatpaks of their applications and make those Flatpaks available for

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

You will be asked for every package installed from updates-testing to provide for updates related to packages or builds that match any of the patterns.

The GHC Haskell compiler will be updated from minor version 8.10.5 to 8.10.7, and Haskell packages will be updated to Stackage LTS 18.28 minor versions.

Assorted information related to the Fedora Linux kernel. ...tiple major kernel versions throughout its life cycle. This wiki page used to list versions but it was frequently out of date.

...sion 9.2 to 9.4, and Haskell packages will be updated from Stackage LTS 20 to LTS 21 versions. ..., 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.

You will be asked for every package installed from updates-testing to provide for updates related to packages or builds that match any of the patterns.

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

...all communication about no frozen rawhide now, and Alpha Freeze/branch in the future ...We should clarify why this process happens the way it does, and what led to this redesign.}}

= Modular Release = ...release, distribution, and update changes associated with and required for the [[Changes/Modular_Server]] and [[Changes/Host_and_Platform]] Changes.

...g them from happening again. When a new issue comes up, it should be added to this page. If you know of one not noted here, please do add it. ...sers. It's sorted in 'most recent first', so new issues should be added to the top.

Update Pyramid (package `python-pyramid` within Fedora) to latest major version. <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Change how we build Flatpaks in Fedora to remove the dependency on modularity. Instead of using modules to rebuild Fedora packages with prefix=/app,

.... It is not a guide to using the Fedora package source control system: see the [[Package maintenance guide]] for that. ...for updates at various stages of the [[Fedora Release Life Cycle]], refer to [[Updates Policy]].

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> Tooling changes to support the new way of branching for Fedora 27

<!-- All fields on this form are required to be accepted by FESCo. We also request that you maintain the same order of sections so that all of the feature pages are uniform. -->

<!-- All fields on this form are required to be accepted by FESCo. We also request that you maintain the same order of sections so that all of the feature pages are uniform. -->

== Notes == Main points of the policy

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

.... It is not a guide to using the Fedora package source control system: see the [https://docs.fedoraproject.org/en-US/package-maintainers/Package_Maintenan ...r updates at various stages of the [[Fedora Release Life Cycle]], refer to the [https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ Updates Policy]

...nge anything, change the original Feature page and it will be picked up in the next refresh. If not, ping jkurik. ...ing_Steering_Committee |Engineering Steering Committee]] for the Fedora 25 Release as System Wide Changes.

Update RPM to the [https://rpm.org/wiki/Releases/4.19.0 4.19] release. <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

...to my joining Red Hat in May 2012 to work on NetworkManager. I was already a Fedora user and package maintainer at that time. Since August 2013 I'm work * [[Networking]] – A starting point for information related to networking.