On 2015-09-16 3:00 PM, Edgar Magana wrote: > Do not do that!!! > > Fix the bug upstream and then back port your commit. > > https://wiki.openstack.org/wiki/How_To_Contribute > http://docs.openstack.org/infra/manual/developers.html > I think he is referring to the "What packages does this deployment size use?" question from "Packaging" section found in the User Survey [1]. Operators and deployers will often package their own versions to get bugfixes or features more quickly than the upstream package can do. (See results for the "If you have modified packages or have built your own packages, why?") Unfortunately the packaging and patching process isn't a turn-key solution. Each operators developed their own. Some open-sourced their solution [2][3] which might or not answer your needs. This explains why we are still having "Packaging" sessions in the OpenStack Ops Meetup. We use a manual process with imply importing and forking Ubuntu packages and applying our own patches in debian/patches. The packages are then built and published by Jenkins. [1] http://superuser.openstack.org/articles/openstack-users-share-how-their-deployments-stack-up [2] https://github.com/blueboxgroup/giftwrap [3] https://github.com/rconradharris/ply -- Mathieu