<div class=”hs-featured-image-wrapper”>
<a href=”https://blog.domainsi.com/blog/understanding-agile-release-update-packs” title=”” class=”hs-featured-image-link”> <img src=”https://blog.domainsi.com/hubfs/S-Marketing%20Content/Images/Fish%20Upgrading.jpg?t=1526322082303″ alt=”Fish Upgrading.jpg” class=”hs-featured-image” style=”width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;”> </a>
</div>
<p>Last year,&nbsp;<a href=”https://community.oracle.com/docs/DOC-1014756″><span style=”text-decoration: underline;”>Oracle announced</span>&nbsp;</a>an important developmental milestone, which affects users of their best-of-breed PLM platform, Agile.&nbsp; They are called Agile Release Update Packs (or RUPs) and the implications of this change carry some weight, both in the now, and well into the future.</p>
<img src=”https://track.hubspot.com/__ptq.gif?a=2252835&amp;k=14&amp;r=https%3A%2F%2Fblog.domainsi.com%2Fblog%2Funderstanding-agile-release-update-packs&amp;bu=https%253A%252F%252Fblog.domainsi.com%252Fblog&amp;bvt=rss” alt=”” width=”1″ height=”1″ style=”min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; “>