<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Release Management Access Control</title>
	<atom:link href="http://allscm.com/archives/release-management-access-control.html/feed" rel="self" type="application/rss+xml" />
	<link>http://allscm.com/archives/release-management-access-control.html</link>
	<description>SCM Unleashed!</description>
	<lastBuildDate>Wed, 17 Feb 2010 12:11:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Angelo</title>
		<link>http://allscm.com/archives/release-management-access-control.html/comment-page-1#comment-40</link>
		<dc:creator>Angelo</dc:creator>
		<pubDate>Tue, 02 Jun 2009 11:49:44 +0000</pubDate>
		<guid isPermaLink="false">http://allscm.com/?p=142#comment-40</guid>
		<description>Completely agree on this.
In my organization we have a delivery process (maintened by SCM) with tools that handle it.
Builds first are delivered to Dev/QA, then the software is made available to System Verification only if QA gives OK. Then sw is delivered to customers only if SV gives OK.</description>
		<content:encoded><![CDATA[<p>Completely agree on this.<br />
In my organization we have a delivery process (maintened by SCM) with tools that handle it.<br />
Builds first are delivered to Dev/QA, then the software is made available to System Verification only if QA gives OK. Then sw is delivered to customers only if SV gives OK.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
