<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>openstack/zaqar — Stackers Network</title>
    <link>https://stackers.network/projects/openstack-zaqar/</link>
    <description>Weekly code-activity digest for openstack/zaqar from Stackers Network.</description>
    <item>
      <title>openstack/zaqar — Week of 2026-05-30</title>
      <link>https://stackers.network/projects/openstack-zaqar/2026-05-30</link>
      <guid>https://stackers.network/projects/openstack-zaqar/2026-05-30</guid>
      <pubDate>Sat, 30 May 2026 00:00:00 +0000</pubDate>
      <description>DevStack plumbing. The bulk of the week reshaped how Zaqar's DevStack plugin pulls in dependencies: library installation from source was refactored, the python-zaqarclient install now happens from source only when explicitly requested, detection of the zaqar-ui directory was…</description>
      <content:encoded><![CDATA[<p><strong>DevStack plumbing.</strong> The bulk of the week reshaped how Zaqar's DevStack plugin pulls in dependencies: library installation from source was <a href="https://review.opendev.org/c/openstack/zaqar/+/989880">refactored</a>, the python-zaqarclient install now happens from source only when explicitly requested, detection of the <code translate="no">zaqar-ui</code> directory was fixed, the global debug flag is now honored, and an unused variable was dropped. A stray <code translate="no">apt-key</code> usage was replaced as part of the same cleanup pass.</p>
<p><strong>Maintenance.</strong> Python 3.10 support was removed and the test script's Ubuntu 22.04 path was dropped, aligning the supported platform matrix with current OpenStack baselines. Constants were introduced for retry backoff functions, the checksum calculation was annotated as non-security, an ineffective check was deleted, and grenade tests are now skipped for tools-only updates.</p>
<p><strong>Bug fixes.</strong> Small correctness fixes landed for a broken log format string and a unit test failure.</p>
<p>Activity this cycle came entirely from a single contributor across 14 small patches totalling under 200 lines — a focused housekeeping week with no functional driver or API changes.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
