<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>ProjectLocker Blog: Subversion 1.5 Upgrade</title>
    <link>http://blog.projectlocker.com/articles/2008/09/05/subversion-1-5-upgrade</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>Subversion 1.5 Upgrade</title>
      <description>&lt;p&gt;We have received many inquiries regarding our plans for Subversion 1.5 at ProjectLocker.&amp;nbsp; I&amp;#39;d like to take a moment to outline our plans specific to Subversion 1.5, as well as present the guidelines that we use to schedule upgrades to major system components. &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Our guideline at ProjectLocker is to allow at least 60 days of burn-in for any major software release.&amp;nbsp; This allows other users to put the software to real-world tests in a variety of environments.&amp;nbsp; It also typically allows any major issues to be discovered, and often resolved with an update release.&amp;nbsp; Most well-supported open source software will generally stabilize within this time period, and the pace of updates will slow as development shifts to the next major version.&amp;nbsp; Our goal behind this process is to ensure that any software that we put into production for our users is stable and unlikely to cause them major problems.&amp;nbsp; Our aim is definitely not to be on the bleeding edge, but rather to be running a still-current version of all of our platform software.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;In that light, our observation period for Subversion 1.5 is nearing its end.&amp;nbsp; Our current plan is to upgrade our servers to Subversion 1.5.2 on October 11.&amp;nbsp; Unless there are major new flaws discovered in the 1.5 line, we will send a note to our customers with details of the maintenance window we schedule for the upgrade (you will not get this notification unless you are on our maintenance mailing list).&amp;nbsp; If there are major new flaws, or if 1.5.3 is released in the interim, we will make a determination as to how to proceed depending on the speciics.&amp;nbsp; However, at this time we are building our plans around October 11.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;Note that you &lt;strong&gt;will not&lt;/strong&gt; have to upgrade your client when our servers migrate to 1.5, unless you plan to take advantage of certain 1.5 features.&amp;nbsp; (See the &lt;a href="http://subversion.tigris.org/svn_1.5_releasenotes.html"&gt;release notes&lt;/a&gt; for details.) &lt;/p&gt;

</description>
      <pubDate>Fri, 05 Sep 2008 18:03:00 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:3c587a3c-dcbe-420b-bfc6-183a6a5669cc</guid>
      <author>Runako Godfrey</author>
      <link>http://blog.projectlocker.com/articles/2008/09/05/subversion-1-5-upgrade</link>
    </item>
    <item>
      <title>"Subversion 1.5 Upgrade" by Runako Godfrey</title>
      <description>&lt;p&gt;Scott --  While we&amp;#39;d certainly like all existing customers to be on our maintenance mailing lists, quite a few of our users have requested the ability to opt out of the maintenance emails.  As a result, users have to manually add themselves to the maintenance list.     Here&amp;#39;s how to do this:   &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;1) Log into the ProjectLocker Portal (My ProjectLocker for Enterprise customers). &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;2) Click the Edit Profile link on the left under User Links.   &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;3) Check the desired boxes under Mailing Lists, and then click Save Changes.   That&amp;#39;s all there is to it!  &lt;/p&gt;</description>
      <pubDate>Mon, 08 Sep 2008 16:26:35 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:abb5c4ec-7a62-406f-a4cd-8245bf5882a7</guid>
      <link>http://blog.projectlocker.com/articles/2008/09/05/subversion-1-5-upgrade#comment-5064</link>
    </item>
    <item>
      <title>"Subversion 1.5 Upgrade" by Scott</title>
      <description>I take it as an existing customer I will already be on the maintenance mailbing list?

If not how do you get on it?

(thought I'd ask here in case anyone else is thinking the same)</description>
      <pubDate>Sun, 07 Sep 2008 03:35:31 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:2924a738-82f6-4e41-8ffd-9375a7af0c10</guid>
      <link>http://blog.projectlocker.com/articles/2008/09/05/subversion-1-5-upgrade#comment-5032</link>
    </item>
  </channel>
</rss>
