<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CKAN: Ticket #803: Auto-generate next migration version unit and test stub files</title>
    <link>http://localhost/ticket/803</link>
    <description>&lt;p&gt;
As a system developer, I want to run 'create next migration version' script, so that I don't have to create migration version tests and files manually.
&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/803</link>
    </image>
    <generator>Trac 0.12.3</generator>
    <item>
      
        <dc:creator>johnbywater</dc:creator>

      <pubDate>Thu, 11 Nov 2010 14:47:46 GMT</pubDate>
      <title>milestone deleted</title>
      <link>http://localhost/ticket/803#comment:1</link>
      <guid isPermaLink="false">http://localhost/ticket/803#comment:1</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;milestone&lt;/strong&gt;
                &lt;em&gt;ckan v1.3&lt;/em&gt; deleted
            &lt;/li&gt;
          &lt;/ul&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>dread</dc:creator>

      <pubDate>Thu, 11 Nov 2010 15:23:44 GMT</pubDate>
      <title></title>
      <link>http://localhost/ticket/803#comment:2</link>
      <guid isPermaLink="false">http://localhost/ticket/803#comment:2</guid>
      <description>
        &lt;p&gt;
I'm not sure a template is needed for the test script - surely repeated stuff can just be factored out?
&lt;/p&gt;
&lt;p&gt;
Creating the model dump file:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;'hg up' to ckan as it was at the last model migration
&lt;/li&gt;&lt;li&gt;'paster db clean', 'paster db init', 'paster create-test-data'
&lt;/li&gt;&lt;li&gt;'pgdump'
&lt;/li&gt;&lt;li&gt;'hg up default'
&lt;/li&gt;&lt;li&gt;Check in the dumped file
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Do we really want a script to mess with our repo like this? Isn't it just safer to do manually with good instructions?
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>thejimmyg</dc:creator>

      <pubDate>Fri, 07 Jan 2011 15:17:15 GMT</pubDate>
      <title>owner, priority, component set</title>
      <link>http://localhost/ticket/803#comment:3</link>
      <guid isPermaLink="false">http://localhost/ticket/803#comment:3</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;owner&lt;/strong&gt;
              set to &lt;em&gt;thejimmyg&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;priority&lt;/strong&gt;
                set to &lt;em&gt;major&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;component&lt;/strong&gt;
                set to &lt;em&gt;ckan&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
      </description>
      <category>Ticket</category>
    </item><item>
      
        <dc:creator>dread</dc:creator>

      <pubDate>Mon, 22 Aug 2011 16:44:11 GMT</pubDate>
      <title>status changed; repo, theme, resolution set</title>
      <link>http://localhost/ticket/803#comment:4</link>
      <guid isPermaLink="false">http://localhost/ticket/803#comment:4</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;repo&lt;/strong&gt;
                set to &lt;em&gt;ckan&lt;/em&gt;
            &lt;/li&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;theme&lt;/strong&gt;
                set to &lt;em&gt;none&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;resolution&lt;/strong&gt;
                set to &lt;em&gt;invalid&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
We now use nose to test migrations instead.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>