<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Transition Technology: Ticket Query</title>
    <link>http://localhost:8080/trac/query?status=closed&amp;component=Trac&amp;milestone=PSE&amp;group=resolution&amp;desc=1&amp;order=priority</link>
    <description>Support and issues tracking for the Transition Network Web Project.</description>
    <language>en-US</language>
    <image>
      <title>Transition Technology</title>
      <url>/trac/chrome/site/TransitionNetwork-Logo-Web-Small.jpg</url>
      <link>http://localhost:8080/trac/query?status=closed&amp;component=Trac&amp;milestone=PSE&amp;group=resolution&amp;desc=1&amp;order=priority</link>
    </image>
    <generator>Trac 0.12.5</generator>
    <item>
        <link>http://localhost:8080/trac/ticket/364</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/364</guid>
        <title>#364: Migrate from SVN to Git</title>
        <pubDate>Fri, 21 Oct 2011 10:56:18 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
SVN smells. Git rules.
&lt;/p&gt;
&lt;p&gt;
OK, so we need to get a publicly available Git repo in place and move to a modern workflow after importing the existing SVN stuff.
&lt;/p&gt;
&lt;p&gt;
Urgent tasks:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Chris: Tell me where you want to put the master repo? In kiwi:/web or somewhere else?
&lt;/li&gt;&lt;li&gt;Chris: add Trac Git plugin: &lt;a class="ext-link" href="http://trac-hacks.org/wiki/GitPlugin"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://trac-hacks.org/wiki/GitPlugin&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;Jim: import from svn repo to new git master using attached users mapping and this process: &lt;a class="ext-link" href="http://www.jonmaddox.com/2008/03/05/cleanly-migrate-your-subversion-repository-to-a-git-repository/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.jonmaddox.com/2008/03/05/cleanly-migrate-your-subversion-repository-to-a-git-repository/&lt;/a&gt; (except it's &lt;tt&gt;git svn&lt;/tt&gt; not &lt;tt&gt;git-svn&lt;/tt&gt; per the article)
&lt;/li&gt;&lt;li&gt;Jim &amp;amp; Chris: look into best way to clone the repo over the existing structure without affecting the LIVE site
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Then later:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Jim: look at best workflow practices for importing direct from Drupal.org for core and contrib, plus managing the code in a multi-developer environment.
&lt;/li&gt;&lt;li&gt;Jim: update documentation with new Git workflow
&lt;/li&gt;&lt;li&gt;Chris: once proven to work, remove SVN cruft from sites directories.
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
The rough plan:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;A new Transition git master repository lives on Kiwi as the SVN repo does today.
&lt;/li&gt;&lt;li&gt;Developers clone it onto their machine, do changes, push/commit them back to master
&lt;/li&gt;&lt;li&gt;DEV and TEST sites use a plain &lt;tt&gt;git pull&lt;/tt&gt; from the master
&lt;/li&gt;&lt;li&gt;LIVE uses tagged releases only.
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
&lt;/p&gt;
&lt;p&gt;
Comments, issues, ideas?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/364#changelog</comments>
    </item>
 </channel>
</rss>