<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Release Engineering on Phosphor BBS</title>
		<link>https://phosphorbbs.net/tags/release-engineering/</link>
		<description>Recent content in Release Engineering on Phosphor BBS</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Wed, 23 Sep 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://phosphorbbs.net/tags/release-engineering/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Publishing 0.1.1: The Deploy That Exited 0 and Published Nothing</title>
				<link>https://phosphorbbs.net/blog/publishing-0-1-1-the-deploy-that-exited-zero/</link>
				<pubDate>Wed, 23 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://phosphorbbs.net/blog/publishing-0-1-1-the-deploy-that-exited-zero/</guid>
				<description>&lt;p&gt;jterm 0.1.1 is on Maven Central. The build that put it there was green in seventeen seconds of test time — and took nine and a half minutes of wall clock, plus a mid-flight correction when we discovered the first deploy had quietly published nothing at all. This post is the release notes for the &lt;em&gt;process&lt;/em&gt;, because the failure mode is one every maintainer of a Central-published library will hit.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
