<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Compare and deploy packages out of sequence</title><link>https://community.appian.com/discussions/f/general/30506/compare-and-deploy-packages-out-of-sequence</link><description>We have compare and deploy set up between Dev and Test. Packages can only be deployed after manager approval. 
 Let&amp;#39;s say package 1 contains ABC Process (version 1). This package is submitted for approval. Later, package 2 is created and contains ABC</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Compare and deploy packages out of sequence</title><link>https://community.appian.com/thread/121248?ContentTypeID=1</link><pubDate>Wed, 01 Nov 2023 16:21:11 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:67c5a556-61a6-479d-893e-bca5d3c577a3</guid><dc:creator>Mike Schmitt</dc:creator><description>&lt;p&gt;The latest version of any object (including process models) is always deployed when doing a compare-and-deploy operation.&amp;nbsp; The deployment system doesn&amp;#39;t know (or care) what approval stage you&amp;#39;re in on the design side, so your development practices will need to take this into account.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>