# release engineering Published articles for release engineering. 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. ## FreeBSD Foundation Welcomes New Board Member: Dave Cottlehuber DevFeed: [FreeBSD Foundation Welcomes New Board Member: Dave Cottlehuber]() Original publisher: [Read original article]() Author: Anne Dickison Published: 2026-07-17T01:32:52Z Content type: news Language: en Sources: [FreeBSD Foundation]() Topics: [freebsd](), [Open Source](), [release engineering](), [Unix]() Tags: [2026](), [blog](), [community](), [foundation](), [freebsd](), [open-source](), [release-engineering]() ### AI overview Dave Cottlehuber was elected to the FreeBSD Foundation Board on June 15, 2026. In an interview, he discusses his path from OpenBSD and UNIX experience to FreeBSD, his community involvement, and his motivation to serve on the board. ### Source excerpt FreeBSD Community member and former Core Representative, Dave Cottlehuber, was elected to the FreeBSD Foundation Board during the Annual Meeting on June 15, 2026. We sat down with Dave to learn more about his history with FreeBSD and what he's most looking forward to accomplishing during his tenure. Tell us a little about yourself, and how [...] The post FreeBSD Foundation Welcomes New Board Member: Dave Cottlehuber first appeared on FreeBSD Foundation. ## 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. ## Go 1.26.2: Security Fixes, Regression Patches, Upgrade Playbook DevFeed: [Go 1.26.2: Security Fixes, Regression Patches, Upgrade Playbook]() Original publisher: [Read original article]() Author: ratneshmaurya2311@gmail.com (Ratnesh Maurya) Published: 2026-04-09T00:00:00Z Content type: release Language: en Sources: [Ratn Labs]() Topics: [Go Language](), [upgrade](), [patches](), [Security]() Tags: [backend](), [beginner](), [go](), [go-security-backend-release-engineering](), [golang](), [patches](), [release-engineering](), [security](), [technical](), [upgrade]() ### AI overview This article covers the Go 1.26.2 release, including its security fixes and regression patches, and provides guidance for upgrading safely in production. ### Source excerpt A beginner-friendly and technical deep dive into Go 1.26.2: what changed, why it matters, and how to upgrade safely in production. ## Streamlining GraphQL Service Testing with Karate DevFeed: [Streamlining GraphQL Service Testing with Karate]() Original publisher: [Read original article]() Author: Armin Aminian SRE; Cloud Native technologies GitHub profile Linkedin profile Published: 2024-07-08T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [GraphQL](), [Testing](), [Microservice](), [API](), [gateway]() Tags: [api](), [architecture](), [backend](), [devops](), [gateway](), [graphql](), [integrity](), [microservice-architecture](), [quality-assurance](), [release-engineering](), [rest](), [schema](), [services](), [testing]() ### AI overview The article describes trivago's move from a GraphQL monolith to a federated microservice architecture and explains the testing challenges this creates. It covers complex nested queries, schema validation, relationships, data integrity, and GraphQL's partial-data error responses. ### Source excerpt Over the last year trivago refactored the existing GraphQL monolith and moved to a microservice architecture, in what is also known as a federated setup. Federated GraphQL, as championed by Apol... ## 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 ## It all started with a commit: Celebrating 6 years of Distroless DevFeed: [It all started with a commit: Celebrating 6 years of Distroless]() Original publisher: [Read original article]() Published: 2023-04-12T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [distroless](), [Containers](), [supply-chain-security](), [container images](), [sigstore](), [chainguard images](), [Kubernetes](), [vulnerability](), [bazel](), [Debian](), [vulnerability management](), [Go]() Tags: [bazel](), [c-plus-plus](), [chainguard](), [chainguard-images](), [containers](), [debian](), [digital-signatures](), [distroless](), [distroless-containers](), [go](), [java](), [kubernetes](), [python](), [release-engineering](), [sigstore](), [software-supply-chain-security](), [verify](), [vulnerability](), [vulnerability-management]() ### AI overview The article commemorates six years of Distroless, describing its goal of creating more secure and efficient container images by removing non-essential components. It covers the Bazel-based build tooling, language runtimes, Kubernetes adoption, vulnerability-management benefits, and later integration with Sigstore for container signing and authenticity verification. It also introduces the subsequent development of Chainguard Images. ### Source excerpt The goal of Distroless is to provide a more secure and efficient way to package and run software in containers by using only essential components. ## 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" ## Interview for BrowserStack's Breakpoint 2020 Conference DevFeed: [Interview for BrowserStack's Breakpoint 2020 Conference]() Original publisher: [Read original article]() Author: Matthias Endler Published: 2020-07-03T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Testing](), [Test automation](), [Continuous Delivery (CD)](), [Cucumber](), [Open Source]() Tags: [bdd](), [conference](), [continuous-delivery](), [engineering-culture](), [interview](), [open-source](), [qa](), [release-engineering](), [test-automation](), [testing]() ### AI overview This article announces Benjamin Bischoff's BrowserStack interview and talk for the virtual Breakpoint 2020 testing summit. It introduces his work in test automation at trivago and describes the company's technical and procedural changes toward more efficient continuous delivery. ### Source excerpt After 15 years as a game/application developer and trainer, Benjamin decided to make test automation his career. He's currently a Test Automation Engineer in trivago's core QA team. Benj... ## Automating mobile app releases for iOS and Android at Badoo DevFeed: [Automating mobile app releases for iOS and Android at Badoo]() Original publisher: [Read original article]() Author: saliery (Badoo) Published: 2020-07-02T13:36:17Z Content type: tutorial Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [iOS](), [App](), [Google Play](), [LineageOS]() Tags: [android](), [app](), [app-store](), [badoo](), [devops](), [fastlane](), [google-play](), [ios](), [re](), [release](), [release-engineering](), [teamcity]() ### AI overview A Badoo release engineer describes the company's automation of iOS and Android app releases. The process automates app-store metadata uploads and enables employees involved in the process to release applications in a few clicks; the release-engineering team reported saving about 830 hours in 2019. ### Source excerpt Всем привет! Меня зовут Михаил Булгаков (нет, не родственник), я работаю релиз-инженером в Badoo. Пять лет назад я занялся автоматизацией релизов iOS-приложений, о чём подробно рассказывал в этой статье. А после взялся и за Android-приложения. Сегодня я подведу некоторые итоги: расскажу, к чему мы пришли за это время. Long story short: любой причастный к процессу сотрудник может зарелизить хоть все наши приложения на обеих платформах в несколько кликов -- без головной боли, больших затрат времени, регистрации и СМС. Так, наш отдел релиз-инженеров за 2019 год сэкономил около 830 часов. За подробностями -- добро пожаловать под кат! Читать дальше -> ## Makefiles in 2019 -- Why They Still Matter DevFeed: [Makefiles in 2019 -- Why They Still Matter]() Original publisher: [Read original article]() Author: Simon Brüggen Professional Makefile guru; Jenkins wrangler Follow Published: 2019-12-20T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [make](), [Microservices](), [Cloud](), [AWS CloudFormation](), [Amazon EC2](), [AWS IAM]() Tags: [aws-cloudformation](), [backend](), [build](), [cloud](), [devops](), [ec2](), [iam](), [make](), [microservices](), [release-engineering]() ### AI overview The article explains how Makefiles can support the development, testing, packaging, and deployment of cloud-based microservices. It highlights the risks of relying on manual README instructions, including outdated documentation, guesswork, and trial-and-error when deploying projects with AWS CloudFormation, EC2, and IAM. ### Source excerpt Make was created in 1976 by Stuart Feldman at Bell Labs to help build C programs. But how can this 40+ year old piece of software help us develop and maintain our ever-growing amount of cloud-based microservices? ## How trivago performs non-functional testing on every commit DevFeed: [How trivago performs non-functional testing on every commit]() Original publisher: [Read original article]() Author: Frank Van Gemeren Published: 2018-10-12T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Testing](), [web applications](), [Scalability](), [Accessibility](), [Availability]() Tags: [accessibility](), [availability](), [backend](), [code-coverage](), [devops](), [frontend](), [release-engineering](), [scalability](), [testing](), [web](), [web-applications]() ### AI overview This article explains why testing should cover non-functional requirements such as performance, capacity, availability, scalability, and accessibility. It describes trivago's approach to making non-functional testing visible to developers on every commit and discusses the challenges of providing early feedback in a large codebase. ### Source excerpt Testing your functionality is important, but what happens if other factors come into play? In this blog post we show how trivago handles non-functional testing for every commit and how we scaled it. ## Automating trivago's Tech Blog Deployment Process DevFeed: [Automating trivago's Tech Blog Deployment Process]() Original publisher: [Read original article]() Author: Busra Koken Software; Backend Engineer; Learning Every Day; Writing Stories Published: 2017-12-07T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Deployment](), [Automation](), [Hugo](), [Jenkins](), [GitHub Pages](), [Markdown](), [DevOps](), [Pull Request](), [Code review]() Tags: [automation](), [backend](), [code-review](), [deployment](), [devops](), [github-pages](), [hugo](), [markdown](), [release-engineering]() ### AI overview This article explains how trivago maintained its Hugo-generated tech blog, hosted it on GitHub Pages, and automated its deployment process. It describes the previous manual workflow, its bottlenecks, and improvements including storing a Jenkins pipeline in the blog repository. ### Source excerpt We do think that our tech blog is full of interesting things powered by our engineers' great stories. Let us take you on a journey of how we maintain trivago tech blog from the technical perspective and how we recently automated its deployment process. ## How we got rid of 5k lines of our bash release process DevFeed: [How we got rid of 5k lines of our bash release process]() Original publisher: [Read original article]() Author: Olaf Gladis Follow Published: 2017-10-16T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [releases](), [Scripting, bash](), [Development](), [Server]() Tags: [bash](), [development](), [devops](), [legacy](), [load-balancer](), [open-source](), [redis](), [release](), [release-engineering](), [rewrite](), [server]() ### AI overview A trivago engineer describes replacing a fragile Bash-based release process. The article covers OPcache warmup failures, manual server recovery, and the legacy deployment tool's maintenance, validation, coupling, and testing problems. ### Source excerpt When I joined trivago a year ago we had problems with our releases. Read how we were able to switch from our bash release process to a new one.