# release engineering Release engineering is a software engineering discipline focused on building and delivering software through version control, building, testing, deployment, and release. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Fedora Forge Usage Policy DevFeed: [Fedora Forge Usage Policy]() Original publisher: [Read original article]() Author: amoloney Published: 2026-07-30T12:11:59Z Content type: article Language: en Sources: [Fedora Community Blog]() Topics: [Fedora](), [forgejo](), [hosting](), [configuration-management](), [release engineering]() Tags: [community](), [configuration-management](), [fedora-project-community](), [forge](), [forgejo](), [governance](), [hosting](), [policy](), [release-engineering]() ### AI overview The Fedora Council is opening a minimum two-week public feedback period for a proposed Fedora Forge Usage Policy. The policy defines the Fedora Forge, a Forgejo instance operated by Fedora Infrastructure, as project infrastructure for hosting Fedora code, documentation, and tooling rather than a general-purpose public Git host. ### Source excerpt After extensive review and discussion on the ticket request and in recent council meetings (see meetbot for 29 July and 15 July 2026), the Fedora Council would like to initiate the policy change policy process for ratifying the Fedora Forge Usage policy. This document is open to public feedback (if any) for a minimum of [...] The post Fedora Forge Usage Policy appeared first on Fedora Community Blog. ## End of Community update DevFeed: [End of Community update]() Original publisher: [Read original article]() Author: zlopez Published: 2026-07-24T12:00:00Z Content type: release Language: en Sources: [Fedora Community Blog]() Topics: [Fedora](), [release engineering]() Tags: [community-update](), [fedora-project-community](), [release](), [updates]() ### AI overview Fedora announces that its Community weekly updates are being replaced by This Week in Fedora, which includes the sources used for the reports. ### Source excerpt Last few years a small team of people in the CLE Team were working each week to prepare a Community update for you. First one published on October 21st 2021. We were starting with only Infrastructure and Release Engineering teams (+ initiatives we did in CPE Team at the time), but later added more teams [...] The post End of Community update appeared first on Fedora Community Blog. ## Community Update - Week 27 DevFeed: [Community Update - Week 27]() Original publisher: [Read original article]() Author: lenkaseg Published: 2026-07-03T11:00:00Z Content type: news Language: en Sources: [Fedora Community Blog]() Topics: [Fedora](), [release engineering](), [RISC-V](), [forgejo](), [scaleway]() Tags: [ai](), [centos-stream](), [community-update](), [fedora-project-community](), [forgejo](), [hardware](), [release-engineering](), [report](), [risc-v](), [scaleway]() ### AI overview A Fedora CLE Team report covering community work from 29 June to 3 July 2026. It summarizes infrastructure operations, CentOS infrastructure, release engineering, RISC-V hardware and builder efforts, migration work, process discussions, packager 2FA discussions, meetings, and an AI-related script improvement. ### Source excerpt This is a report created by CLE Team, which is a team containing community members working in various Fedora groups for example Infrastructure, Release Engineering, Quality etc. This team is also moving forward some initiatives inside Fedora project. Week: 29 June - 3 July 2026 Fedora Infrastructure This team is taking care of day to [...] The post Community Update - Week 27 appeared first on Fedora Community Blog. ## Community Update - Week 26 2026 DevFeed: [Community Update - Week 26 2026]() Original publisher: [Read original article]() Author: zlopez Published: 2026-06-26T10:00:00Z Content type: article Language: en Sources: [Fedora Community Blog]() Topics: [Fedora](), [release engineering](), [centos](), [Ansible](), [RabbitMQ]() Tags: [2026](), [ansible](), [centos-stream](), [community-update](), [fedora-project-community](), [infrastructure](), [network](), [rabbitmq](), [release-engineering]() ### AI overview The CLE Team reports on Fedora and CentOS infrastructure work during 22-26 June 2026. The update covers service operations, packaging and dependency rebuilds, signing infrastructure changes, API-key rotation, DHCP migration work, staging issues involving RabbitMQ, and hardware firmware discussions. ### Source excerpt This is a report created by CLE Team, which is a team containing community members working in various Fedora groups for example Infrastructure, Release Engineering, Quality etc. This team is also moving forward some initiatives inside Fedora project. Week: 22 - 26 June 2026 Fedora Infrastructure This team is taking care of day to day [...] The post Community Update - Week 26 2026 appeared first on Fedora Community Blog. ## Community Update - Week 25, 2026 DevFeed: [Community Update - Week 25, 2026]() Original publisher: [Read original article]() Author: jnsamyak Published: 2026-06-23T10:12:46Z Content type: news Language: en Sources: [Fedora Community Blog]() Topics: [Fedora](), [release engineering](), [Cloud](), [openstack](), [qemu](), [Amazon Web Services]() Tags: [2026](), [aws](), [ci](), [cloud](), [community-update](), [fedora-project-community](), [infrastructure](), [maintainers](), [migration](), [openstack](), [qemu](), [release-engineering](), [report](), [test]() ### AI overview A Fedora CLE Team report covering infrastructure and CentOS operations during 15-19 June 2026, including service moves, operating-system upgrades, repository security work, migrations, load-balancer changes, release engineering, and quality initiatives. ### Source excerpt This is a report created by CLE Team, which is a team containing community members working in various Fedora groups for example Infrastructure, Release Engineering, Quality etc. This team is also moving forward some initiatives inside Fedora project. Week: 15 - 19 June 2026 (Flock Week!!) Fedora Infrastructure This team is taking care of day [...] The post Community Update - Week 25, 2026 appeared first on Fedora Community Blog. ## Community Update - Week 24, 2026 DevFeed: [Community Update - Week 24, 2026]() Original publisher: [Read original article]() Author: jnsamyak Published: 2026-06-23T10:07:47Z Content type: article Language: en Sources: [Fedora Community Blog]() Topics: [Fedora](), [release engineering](), [ci]() Tags: [2026](), [blog](), [community](), [community-update](), [fedora-project-community](), [infrastructure](), [release-engineering](), [report]() ### AI overview A weekly Fedora Community Blog report covering work by the CLE Team and related groups from 8-12 June 2026. It summarizes infrastructure and CentOS operations, release engineering, AI experimentation, quality engineering, CI maintenance, test days, package builds, and ongoing issue resolution. ### Source excerpt This is a report created by CLE Team, which is a team containing community members working in various Fedora groups for example Infrastructure, Release Engineering, Quality etc. This team is also moving forward some initiatives inside Fedora project. Week: 08 - 12 June 2026 Fedora Infrastructure This team is taking care of day to day [...] The post Community Update - Week 24, 2026 appeared first on Fedora Community Blog. ## From Contributor to Outreachy Intern: My Fedora Journey Begins DevFeed: [From Contributor to Outreachy Intern: My Fedora Journey Begins]() Original publisher: [Read original article]() Author: Aman . Published: 2026-06-16T12:00:00Z Content type: article Language: en Sources: [Fedora Community Blog]() Topics: [Fedora](), [FastAPI](), [API](), [release engineering](), [Authentication](), [CI/CD](), [forgejo](), [Pydantic](), [Swagger](), [Deployment](), [openid]() Tags: [apis](), [backend](), [blog](), [fedora-project-community](), [intern](), [journey](), [mentored-projects](), [open-source](), [outreachy]() ### AI overview Aman describes his first two weeks as an Outreachy intern with the Fedora community. He introduces the Fedora Release Schedule Planner API project and outlines planned work on testing, CI reliability, OpenID Connect authentication, Fedora infrastructure integration, and deployment preparation. ### Source excerpt Introduction Hi, I'm Aman, a software developer and open-source enthusiast who enjoys backend development, APIs, and building tools that are useful to others. I recently started my Outreachy internship with the Fedora community, and this is my first blog as an intern. In this post, I want to share what my first two weeks have [...] The post From Contributor to Outreachy Intern: My Fedora Journey Begins appeared first on Fedora Community Blog. ## Evolution of Developer Productivity at Square - Part Four DevFeed: [Evolution of Developer Productivity at Square - Part Four]() Original publisher: [Read original article]() Author: Korhan Bircan Published: 2024-02-26T17:00:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [code productivity](), [Testing](), [Test automation](), [release engineering](), [Mobile]() Tags: [crash-reporting](), [developer](), [engineering](), [flaky-tests](), [mobile](), [mobile-performance](), [operational](), [release-engineering]() ### AI overview The fourth and final part of Square's developer productivity series describes its shift toward reliability and test engineering as its codebase and customer base grew. It covers reliability reviews, service-level objectives, performance-focused task forces, mobile release engineering, automated crash reporting, and efforts to improve testing infrastructure and flaky tests. ### Source excerpt Investing in reliability and test engineering ## In Focus: Jay Dihenkar DevFeed: [In Focus: Jay Dihenkar]() Original publisher: [Read original article]() Author: Jacob Published: 2023-02-23T03:01:29Z Content type: opinion Language: en Sources: [Grofers]() Topics: [release engineering](), [SRE](), [CI/CD](), [Resilience](), [Monitoring](), [observability](), [developer-productivity](), [Automation](), [Scalability](), [systems]() Tags: [automation](), [ci-cd](), [culture](), [developer](), [developer-productivity](), [devops](), [monitoring](), [observability](), [people-at-blinkit](), [quick-commerce](), [release-engineering](), [resilience](), [scalability](), [site-reliability-engineer](), [sre](), [systems]() ### AI overview An interview with Blinkit Staff Engineer Jay Dihenkar about his journey from release engineering to site reliability engineering. He discusses CI/CD, developer productivity, production incident debugging, automation, monitoring and alerting, infrastructure costs, application reliability patterns, and challenges in scaling quick-commerce logistics. ### Source excerpt A conversation with engineers who help run Blinkit Jay Dihenkar is a Staff Engineer at Blinkit. He joined us in December 2020 and has helped different teams manage and streamline their build and release processes. He is currently working towards continuously improving the reliability, scalability, observability, developer productivity, and other such aspects of a software system critical for ensuring that the system can meet the needs of its users and stakeholders over time. Tell us something about yourself and your journey in Blinkit so far. I started out as an engineer on the Release Engineering team, working on goals of Software Quality/Stability and streamlining release processes (Continuous Integration/Continuous Deployment or CI/CD). I help make an impact by improving developer productivity while safeguarding the production ecosystem against failures. I later transitioned into the Site Reliability Engineering (SRE) team, where we focused on improving the reliability and resilience of our systems. Being a site-reliability engineer requires one to develop a deep understanding of how the various components of a system work together and how to optimize them. Overall my journey in Blinkit is one of continuous learning and improvement. If you were to describe your experience as a Blinker in one word, what would that be? Growth. Being here is all about continuous learning in a fast-paced environment. What does a typical day at work look like for you? On a typical day, I work on the following domains (though not everything on a single day!): debugging complex problems sprung out of production incidents, putting automation in places where required, setting up monitoring and alerting, as well as responding to alerts, release engineering and developer productivity (CI/CD), System Infrastructure Cost, Working toward implementing Application Reliability Patterns and so on... What are the biggest challenges facing quick commerce today? I believe the "Logistics infrastructure"