<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Build and Release Management &#187; Release Framework</title>
	<atom:link href="http://allscm.com/archives/category/release-framework/feed" rel="self" type="application/rss+xml" />
	<link>http://allscm.com</link>
	<description>SCM Unleashed!</description>
	<lastBuildDate>Tue, 29 Jun 2010 20:13:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Release Management Access Control</title>
		<link>http://allscm.com/archives/release-management-access-control.html</link>
		<comments>http://allscm.com/archives/release-management-access-control.html#comments</comments>
		<pubDate>Thu, 16 Apr 2009 20:10:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Build Framework]]></category>
		<category><![CDATA[Release Framework]]></category>
		<category><![CDATA[SCM Basics]]></category>

		<guid isPermaLink="false">http://allscm.com/?p=142</guid>
		<description><![CDATA[Access Control, at first glance seems to be a rather straight forward topic or task to handle.  Well, I can assure you it is not.  Especially when you&#8217;re working in an Engineering organization that seems to be schizophrenic at times in terms of its own unique identity.   I&#8217;m talking about how there should be [...]


Related posts:<ol><li><a href='http://allscm.com/consulting-services' rel='bookmark' title='Permanent Link: Consulting Services'>Consulting Services</a> <small>Establish An Accurate and Continuous Build and Release Infrastructure For...</small></li>
</ol>]]></description>
		<wfw:commentRss>http://allscm.com/archives/release-management-access-control.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Build Reproducibility Problem</title>
		<link>http://allscm.com/archives/build-reproducibility-problem.html</link>
		<comments>http://allscm.com/archives/build-reproducibility-problem.html#comments</comments>
		<pubDate>Mon, 14 Apr 2008 09:51:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Build Framework]]></category>
		<category><![CDATA[Release Framework]]></category>

		<guid isPermaLink="false">http://allscm.com/?p=69</guid>
		<description><![CDATA[I&#8217;ve seen a lot of organizations running into this problem such that their build environment gets to a point where it is so complicated that the best way to preserve it is through archiving the image.  I&#8217;m talking about archiving the entire build machine using image tools such as Norton Ghost, VMWare, or Microsoft VirtualPC.  [...]


No related posts.]]></description>
		<wfw:commentRss>http://allscm.com/archives/build-reproducibility-problem.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Burnout Factor As a Build and Release Engineer</title>
		<link>http://allscm.com/archives/the-burnout-factor-as-a-build-and-release-engineer.html</link>
		<comments>http://allscm.com/archives/the-burnout-factor-as-a-build-and-release-engineer.html#comments</comments>
		<pubDate>Tue, 15 Jan 2008 09:07:09 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Build Framework]]></category>
		<category><![CDATA[Release Framework]]></category>

		<guid isPermaLink="false">http://allscm.com/?p=47</guid>
		<description><![CDATA[Software Build and Release has such a hectic schedule&#8211;sometimes you just can&#8217;t help it but to get caught in it all and get burned out.  Aside from a successful proposal of a new build and release infrastructure and getting all the development teams on board, the headache starts when the implementation and back-to-back release schedule [...]


No related posts.]]></description>
		<wfw:commentRss>http://allscm.com/archives/the-burnout-factor-as-a-build-and-release-engineer.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Configuration Management Policy</title>
		<link>http://allscm.com/archives/configuration-management-policy.html</link>
		<comments>http://allscm.com/archives/configuration-management-policy.html#comments</comments>
		<pubDate>Thu, 19 Jul 2007 08:14:36 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Automated Test Framework]]></category>
		<category><![CDATA[Build Framework]]></category>
		<category><![CDATA[Continuous Integration]]></category>
		<category><![CDATA[Release Framework]]></category>
		<category><![CDATA[SCM Agile Development]]></category>

		<guid isPermaLink="false">http://allscm.com/?p=23</guid>
		<description><![CDATA[To promote the spirit of Agile Development and Continuous Integration, groups of builds must be classified and treated differently within the development organization. These builds are as follows: Engineering: These builds lives on the individual developer&#8217;s machine. It should never see the light of day beyond this scope. This is merely a convenient build tool [...]


No related posts.]]></description>
		<wfw:commentRss>http://allscm.com/archives/configuration-management-policy.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
