In general, RDO does not carry custom patches that have not yet landed upstream and have been released, except in rare and carefully decided circumstances with consensus from maintainers. This allows RDO to be as "vanilla" as possible and, especially, test with the same content and versions that the greater OpenStack community develops and tests against. So, if you have a bugfix for a package you would like to release in RDO, it needs to: 1) Be merged in the upstream project 2) Be tagged in a dot release targetted at the ongoing stable release (e.g, Ocata) 3) The spec file updated for the release accordingly (example here[1]) 4) The rdoinfo reference to that package updated accordingly for the -testing and -release tags (example here [2]) 5) Once the package has been built, tagged and released, it will be available as a package update from mirror.centos.org For your scenario 2 and 3, the package will be available inside the release's repositories so long as it is packaged and maintained. If a customer upgrades from Ocata to Pike and wants to start using your puppet module, he will be able to. As far as installation and upgrade path, this is handled within the installers (ex: Packstack, TripleO, Kolla), not within RDO itself. RDO provides the packaging and the repositories, not the installation or upgrade mechanisms. [1]: https://github.com/rdo-packages/nova-distgit/commit/823152d9cf26768d16578... [2]: https://github.com/redhat-openstack/rdoinfo/commit/b5bfbe4dea41e448179c34... David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Mon, Jul 17, 2017 at 11:02 AM, Dnyaneshwar Pawar <Dnyaneshwar.Pawar(a)veritas.com&gt; wrote: