<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Issuelane blog</title>
    <link>https://issuelane.cublya.com/blog</link>
    <description>Articles on feature requests, public roadmaps, changelogs and planning.</description>
    <language>en</language>
    <atom:link href="https://issuelane.cublya.com/blog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A changelog RSS feed that works in every reader: a field-by-field checklist</title>
      <link>https://issuelane.cublya.com/blog/changelog-rss-feed-checklist</link>
      <guid isPermaLink="false">blog/changelog-rss-feed-checklist</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate>
      <description>&lt;p&gt;What RSS 2.0 and its best practices profile require of a changelog feed, field by field, and the mistakes that show entries twice or as one run-on paragraph.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Emailing voters when a feature ships: unsubscribe, link scanners and sending once</title>
      <link>https://issuelane.cublya.com/blog/feature-shipped-emails</link>
      <guid isPermaLink="false">blog/feature-shipped-emails</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate>
      <description>&lt;p&gt;Who should get the shipped email, what RFC 8058 one-click unsubscribe requires, why the unsubscribe link must not act on GET, and how to avoid sending twice.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Should search engines index your feature request board?</title>
      <link>https://issuelane.cublya.com/blog/indexing-feature-request-boards</link>
      <guid isPermaLink="false">blog/indexing-feature-request-boards</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate>
      <description>&lt;p&gt;A page-by-page indexing policy for public request boards, roadmaps and changelogs, built from Google&apos;s documentation, with the defaults that hide or leak pages.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Comparing progress across projects that name their workflow states differently</title>
      <link>https://issuelane.cublya.com/blog/workflow-state-categories</link>
      <guid isPermaLink="false">blog/workflow-state-categories</guid>
      <pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate>
      <description>&lt;p&gt;Map every workflow state to one of five categories so WIP, throughput and cycle time compare across projects. A worked example, plus the edge cases.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
