<?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-cinder — Stackers Network</title>
    <link>https://stackers.network/projects/openstack-charm-cinder/</link>
    <description>Weekly code-activity digest for openstack/charm-cinder from Stackers Network.</description>
    <item>
      <title>openstack/charm-cinder — Week of 2026-06-06</title>
      <link>https://stackers.network/projects/openstack-charm-cinder/2026-06-06</link>
      <guid>https://stackers.network/projects/openstack-charm-cinder/2026-06-06</guid>
      <pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate>
      <description>CI cleanup across stable branches. The week was dominated by a sweep of CI refreshes spanning every supported series — Master, Caracal, Bobcat, Antelope, Zed and Yoga each got a dedicated &quot;Cleanup CI&quot; patch, together moving roughly 13,000 lines of test scaffolding. The shape of…</description>
      <content:encoded><![CDATA[<p><strong>CI cleanup across stable branches.</strong> The week was dominated by a sweep of CI refreshes spanning every supported series — Master, Caracal, Bobcat, Antelope, Zed and Yoga each got a dedicated "Cleanup CI" patch, together moving roughly 13,000 lines of test scaffolding. The shape of the diffs (large additions paired with large deletions) points to regenerated bundles and refreshed test matrices rather than functional charm changes. See the Master cut at https://review.opendev.org/c/openstack/charm-cinder/+/990638 for the reference shape.</p>
<p><strong>Tox and requirements refresh.</strong> A parallel set of six patches updated <code translate="no">tox.ini</code> and regenerated requirements across the same branches, with the Master change carrying the bulk of the churn (~800 lines) and the stable backports converging on a small, uniform delta. Two follow-up tweaks rounded out the tox environment: <code translate="no">*_proxy</code> envvars were added to <code translate="no">passenv</code>, and <code translate="no">HOME</code> was propagated to <code translate="no">passenv</code> for classic charms so zaza functional tests can run — backported across five branches.</p>
<p>No functional charm or driver changes landed this week; the activity was entirely gate and tooling maintenance.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
