<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CKAN: Ticket #1284: Lots of revisions being created on datahub.org</title>
    <link>http://localhost/ticket/1284</link>
    <description>&lt;p&gt;
Revisions aren't assigned to packages. Where are they coming from? This seems to have been occurring since the upgrade to 1.4.3b a couple of weeks ago?
&lt;/p&gt;
</description>
    <language>en-us</language>
    <image>
      <title>CKAN</title>
      <url>http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png</url>
      <link>http://localhost/ticket/1284</link>
    </image>
    <generator>Trac 0.12.3</generator>
    <item>
      
        <dc:creator>dread</dc:creator>

      <pubDate>Mon, 05 Sep 2011 08:44:18 GMT</pubDate>
      <title></title>
      <link>http://localhost/ticket/1284#comment:1</link>
      <guid isPermaLink="false">http://localhost/ticket/1284#comment:1</guid>
      <description>
        &lt;p&gt;
Fixed by rgrp in cset:1952445d2802 on release-v1.4.3 and default. Comment:
&lt;/p&gt;
&lt;p&gt;
do not create revision for changes to users as they are not revisioned.
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;This had already been removed in cset:8d6fde0e2196 (then in user controller) but Adria seems to have reinstated this when refactoring things into the logic layer. This 'bug' explains the huge number of empty revisions we have been seeing on ckan.net.
&lt;/li&gt;&lt;/ul&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>dread</dc:creator>

      <pubDate>Mon, 05 Sep 2011 08:50:03 GMT</pubDate>
      <title>status changed; resolution set</title>
      <link>http://localhost/ticket/1284#comment:2</link>
      <guid isPermaLink="false">http://localhost/ticket/1284#comment:2</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;new&lt;/em&gt; to &lt;em&gt;closed&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;resolution&lt;/strong&gt;
                set to &lt;em&gt;fixed&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
I've added tests for this (to prevent yet another regression!) in cset:1b77ce8ce560. Closing.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>rgrp</dc:creator>

      <pubDate>Mon, 05 Sep 2011 09:19:18 GMT</pubDate>
      <title></title>
      <link>http://localhost/ticket/1284#comment:3</link>
      <guid isPermaLink="false">http://localhost/ticket/1284#comment:3</guid>
      <description>
        &lt;p&gt;
I'm not sure this is the sort of thing we need tests for (we can have too many tests!). Something worse discussing ...
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>dread</dc:creator>

      <pubDate>Mon, 05 Sep 2011 09:40:26 GMT</pubDate>
      <title></title>
      <link>http://localhost/ticket/1284#comment:4</link>
      <guid isPermaLink="false">http://localhost/ticket/1284#comment:4</guid>
      <description>
        &lt;p&gt;
Really? How many times do you want to fix this bug again? For the sake of three lines of test...
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>