#releaseengineering — Public Fediverse posts

BSDCan https://www.bsdcan.org/2026/ Talk Friday 2026-06-19: 15:45 - 16:35 DMS 1130
How FreeBSD 15 landed
Colin Percival
https://www.bsdcan.org/2026/timetable/timetable-How-FreeBSD-15.html
To register https://www.bsdcan.org/2026/registration.html @bsdcan #freebsd #releaseengineering

TIL more about git rebase after discussing some design for a backport pattern for one of our work projects. Since we’re a pretty isolated infra team we’re mostly led to our own means for this type of thing.

I think I’m still confused as to when rebase would be preferred to cherry-pick. Pretty sure it would be if you want the entirety of the target vs a specific change in a given commit.

Probably more clear once I make some drawings or a contrived git example.

#git #releaseEngineering

Whatever you do in your #opensource project, when you do a release:

1. Don't just push a tag
2. Package up a proper release with user-friendly tarballs, ChangeLog with relevant information, not just git logs
3. Remember to always do an -rc1 tag

Some like to do -beta and -alpha tags as well, but *at least* do an -rc1 tag and test the resulting artifacts from your project. It's far worse having users report back to you that your stuff doesn't work.

#releaseengineering #AccountabilityMatters

Every single day ... and not simply once per day...

"Was XX made this way specfically as terrible as possible so that I'll eventually give up and buy a YY?"

"Why does XX get worse with every single system update? Do they know anything about regression testing at all?"

"Do they only operate on the idiotic notion of 'Move Fast, Break Everything?' as if we were still in 2009 web2.0 and testing in production? Also, only lazy unimaginative chuds think that everything needs to be tested in production!"

"Do they really think everyone is an A or a B in their poorly conceived deployment process? 'well, some percentage of our users can suffer as long as we remain profitable by ZZ% so we definitely A/B test in production!'"

#software #hardware #engineering #CiCd #stopTestingInProduction #yourCorpIsNotFAANG #yourCorpIsNotMAANG #yourCorpIsNotHyperscalerScale #getOffMyLawn #itsAllJustAssholesAndElbows #failureModeEverywhere #releaseEngineering #softwareTesting #testingEthics #testing #testingMyPatience #tediousHashTagExpressionism #evaOnAnotherRant

Every single day ... and not simply once per day...

"Was XX made this way specfically as terrible as possible so that I'll eventually give up and buy a YY?"

"Why does XX get worse with every single system update? Do they know anything about regression testing at all?"

"Do they only operate on the idiotic notion of 'Move Fast, Break Everything?' as if we were still in 2009 web2.0 and testing in production? Also, only lazy unimaginative chuds think that everything needs to be tested in production!"

"Do they really think everyone is an A or a B in their poorly conceived deployment process? 'well, some percentage of our users can suffer as long as we remain profitable by ZZ% so we definitely A/B test in production!'"

#software #hardware #engineering #CiCd #stopTestingInProduction #yourCorpIsNotFAANG #yourCorpIsNotMAANG #yourCorpIsNotHyperscalerScale #getOffMyLawn #itsAllJustAssholesAndElbows #failureModeEverywhere #releaseEngineering #softwareTesting #testingEthics #testing #testingMyPatience #tediousHashTagExpressionism #evaOnAnotherRant

Every single day ... and not simply once per day...

"Was XX made this way specfically as terrible as possible so that I'll eventually give up and buy a YY?"

"Why does XX get worse with every single system update? Do they know anything about regression testing at all?"

"Do they only operate on the idiotic notion of 'Move Fast, Break Everything?' as if we were still in 2009 web2.0 and testing in production? Also, only lazy unimaginative chuds think that everything needs to be tested in production!"

"Do they really think everyone is an A or a B in their poorly conceived deployment process? 'well, some percentage of our users can suffer as long as we remain profitable by ZZ% so we definitely A/B test in production!'"

#software #hardware #engineering #CiCd #stopTestingInProduction #yourCorpIsNotFAANG #yourCorpIsNotMAANG #yourCorpIsNotHyperscalerScale #getOffMyLawn #itsAllJustAssholesAndElbows #failureModeEverywhere #releaseEngineering #softwareTesting #testingEthics #testing #testingMyPatience #tediousHashTagExpressionism #evaOnAnotherRant

Every single day ... and not simply once per day...

"Was XX made this way specfically as terrible as possible so that I'll eventually give up and buy a YY?"

"Why does XX get worse with every single system update? Do they know anything about regression testing at all?"

"Do they only operate on the idiotic notion of 'Move Fast, Break Everything?' as if we were still in 2009 web2.0 and testing in production? Also, only lazy unimaginative chuds think that everything needs to be tested in production!"

"Do they really think everyone is an A or a B in their poorly conceived deployment process? 'well, some percentage of our users can suffer as long as we remain profitable by ZZ% so we definitely A/B test in production!'"

#software #hardware #engineering #CiCd #stopTestingInProduction #yourCorpIsNotFAANG #yourCorpIsNotMAANG #yourCorpIsNotHyperscalerScale #getOffMyLawn #itsAllJustAssholesAndElbows #failureModeEverywhere #releaseEngineering #softwareTesting #testingEthics #testing #testingMyPatience #tediousHashTagExpressionism #evaOnAnotherRant

Every single day ... and not simply once per day...

"Was XX made this way specfically as terrible as possible so that I'll eventually give up and buy a YY?"

"Why does XX get worse with every single system update? Do they know anything about regression testing at all?"

"Do they only operate on the idiotic notion of 'Move Fast, Break Everything?' as if we were still in 2009 web2.0 and testing in production? Also, only lazy unimaginative chuds think that everything needs to be tested in production!"

"Do they really think everyone is an A or a B in their poorly conceived deployment process? 'well, some percentage of our users can suffer as long as we remain profitable by ZZ% so we definitely A/B test in production!'"

#software #hardware #engineering #CiCd #stopTestingInProduction #yourCorpIsNotFAANG #yourCorpIsNotMAANG #yourCorpIsNotHyperscalerScale #getOffMyLawn #itsAllJustAssholesAndElbows #failureModeEverywhere #releaseEngineering #softwareTesting #testingEthics #testing #testingMyPatience #tediousHashTagExpressionism #evaOnAnotherRant

#ReleaseEngineering, #Microsoft style #MSFS2024

https://youtu.be/xbJ_X05ioAk?si=L24EnfgxfXttnIIY

Curious about the driving forces behind #GCC stability and #LLVM’s rapid innovation? Ever wondered how release strategies impacts Linux distributions? Tom Stellard and David Edelsohn's presentation from US
@llvm DevMtg.
#GCC #LLVM #OpenSource #Linux #Compilers #LTS #ReleaseEngineering
https://www.linkedin.com/feed/update/urn:li:activity:7258183064650936320/

Is there a Release Engineering meetup in London that anyone is aware of?

If not, would you be interested in attending one of there was?

#ReleaseEngineering #RelEng #London #Meetup

TFW some confusing technical point reveals itself and the metaphorical 'a ha' light bulb goes off.

I've been doing computer stuff (mostly #ReleaseEngineering) since 1979 and I still feel that little dopamine rush. It's good stuff.

For any #ReleaseEngineering folks: I've been struggling to come up with a term to describe a generic set of installable packages: rpms, debs, pkgs, msis, etc.

The best I've done is the uninspired "Platform Dependent Software Distribution" which has a rather unfortunate-sounding initialism, especially over zoom.

Anyone have a better one?

This is a summary of the work done by Fedora Infrastructure & Release Engineering teams as of 2023. As these teams are working closely together, we will summarize the work done in one blog post by both teams.

This update is made from infographics and detailed updates. If you want to just see what’s new, check the infographics. If you want more details, continue reading.

About

Purpose of these teams is to take care of day-to-day business regarding Fedora Infrastructure and Fedora Release Engineering work. It’s responsible for developing and maintaining services running in Fedora and preparing things for the new Fedora Linux release (mirrors, mass branching, new namespaces etc.). 

Issue trackers

• Fedora Infrastructure
• Fedora Release Engineering

Closed tickets

• Fedora Infrastructure – 585
• Fedora RelEng – 617

Fedora Infrastructure highlights

• Pagure to GitLab importer tool
• Digicert codesigning alternative
• Update koji messaging schema
• Skeleton for bridge from fasjson groups to discourse
• Flask-OIDC improvement
• ppc64le workers for osbuild
• mdapi rewrite

Fedora Release Engineering highlights

• Automate processing of fedora-scm-requests
• Centralise and update Fedora infra and releng SOPs

Photo by Taylor Vick on Unsplash. Modified by Justin W. Flory. CC BY-SA 4.0.

https://communityblog.fedoraproject.org/2023-year-in-review-infra-releng/

#Fedora39 #FedoraInfrastructure #FedoraLinux38 #Infra #InfraReleng #mdapi #ReleaseEngineering #YearInReview #YearInReview2023

@genehack; @dolmen; @klardotsh

#ReleaseEngineering

By request, my story of deleting the company's source code repository.

The setting: Santa Cruz, California, around 1983. It was late Spring Saturday and instead of frolicking on the beach or in the redwoods, I was at my work in an industrial park just north of town.

The company I worked for was an OEM for Sun Microsystems. We made an ultra-spiff version of a Sun machine, with hot-swappable fault tolerance and other lovely enhancements. 1/

Once again, I'm compiling the new compiler with the old compiler so that the new compiler can compile itself to become the new compiler so that the new compiler can compile cmake which compiles things into a form that the new compiler can compile.

People pay me to do this.

#ReleaseEngineering

Do you have a UX team? A DevOps team? A Platform team? A last-mile UAT team? A Release team? A Support team? Do they work as a boost or a bottleneck for you?

This is an exploration of when/how they are beneficial

#DevOps #PlatformEngineering #ReleaseEngineering #Outsourcing

Hey folks, what #coding for good organizations do you like? I went to #sunlightFoundation but they are defunct and I'm looking for some #opengoverment projects where I can help with my #devops, #python, #groovy, and #releaseEngineering skills

How strict should I be about the pre-release -> alpha -> beta -> rc release cycle? Or can I skip right to beta or rc when doing open beta testing?
https://en.wikipedia.org/wiki/Software_release_life_cycle
#releaseengineering

Talking with @gdinwiddie about how we're still figuring out how to find folks who are interested in #VirginiaSatir and #systemsthinking on this platform reminded my best trick ever for finding other systems thinkers was to get myself on a #releaseengineering team.

I met lots of people that way at #pivotal who were into systems but didn't know yet that there was a word for it. The release teams attracted people who intuitively grasped that you couldn't optimize systems by optimizing parts.