<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>openstack/charm-heat — Stackers Network</title>
    <link>https://stackers.network/projects/openstack-charm-heat/</link>
    <description>Weekly code-activity digest for openstack/charm-heat from Stackers Network.</description>
    <item>
      <title>openstack/charm-heat — Week of 2026-06-06</title>
      <link>https://stackers.network/projects/openstack-charm-heat/2026-06-06</link>
      <guid>https://stackers.network/projects/openstack-charm-heat/2026-06-06</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate>
      <description>Tooling and CI. The week was almost entirely a sweep through the charm's CI configuration across every supported branch. Six &quot;Cleanup CI&quot; patches landed in parallel — covering Master, Caracal, Bobcat, Antelope, Zed, and Yoga — together accounting for roughly 13,000 of the week's…</description>
      <content:encoded><![CDATA[<p><strong>Tooling and CI.</strong> The week was almost entirely a sweep through the charm's CI configuration across every supported branch. Six "Cleanup CI" patches landed in parallel — covering Master, <a href="https://review.opendev.org/c/openstack/charm-heat/+/990564">Caracal</a>, Bobcat, Antelope, Zed, and Yoga — together accounting for roughly 13,000 of the week's ~13,700 churned lines as stale job definitions, fixtures, and bundles were pruned or refreshed branch by branch.</p>
<p><strong>Test environment.</strong> Six <code translate="no">tox.ini</code> refreshes re-generated requirements across the same set of branches, and a follow-up series added <code translate="no">HOME</code> to <code translate="no">passenv</code> for the classic charms so that zaza functional tests can run cleanly. A small companion change adds <code translate="no">*_proxy</code> envvars to tox <code translate="no">passenv</code> on master.</p>
<p><strong>Maintenance.</strong> No feature or bugfix work merged this week — the activity was purely housekeeping across the stable branch matrix.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
