<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>DevOps Tools on Shafiq Alibhai</title>
    <link>https://www.shafiq.in/zh/tags/devops-tools/</link>
    <description>Recent content in DevOps Tools on Shafiq Alibhai</description>
    <generator>Hugo</generator>
    <language>zh-CN</language>
    <copyright>© 2009-2026 All rights reserved.</copyright>
    <lastBuildDate>Wed, 11 May 2011 16:38:57 +0000</lastBuildDate>
    <atom:link href="https://www.shafiq.in/zh/tags/devops-tools/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Practical Guide to Release Engineering - Mastering Version Control with Subversion</title>
      <link>https://www.shafiq.in/zh/blog/a-practical-guide-to-release-engineering-mastering-version-control-with-subversion/</link>
      <pubDate>Wed, 11 May 2011 16:38:57 +0000</pubDate>
      <guid>https://www.shafiq.in/zh/blog/a-practical-guide-to-release-engineering-mastering-version-control-with-subversion/</guid>
      <description>&lt;p&gt;Subversion is more than just a tool for tracking changes in your code. It can be a cornerstone of an effective release engineering strategy, offering features that facilitate a smooth transition of code from development to production. Here, we&amp;rsquo;ll explore two techniques you can employ: utilizing revision numbers and creating tags.&lt;/p&gt;&#xA;&lt;p&gt;Most people who have dabbled in Subversion are familiar with revision numbers. Let&amp;rsquo;s say you make a commit and your code becomes &amp;ldquo;revision 1234.&amp;rdquo; You can then export this specific revision to your development environment for testing. Once it passes your rigorous checks, it&amp;rsquo;s off to the QA environment for further scrutiny.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
