bifrost-release-suggestions

Problem statement: A stable release of Bifrost can break due to dependencies changing.

Background:
We had a bifrost VM which was responsible for deploying baremetals in our lab. We had a version of bifrost locked down 
prior to Mitaka release and it was working fine until we had to tear down the VM and re-create it. We found that 
by default ‘master’ version of ironic sources was used in the setup. This lead to the VM not being setup properly. 
On suggestions from the community, we pegged bifrost, ironic and ironic-client to ‘stable/mitaka’ and that 
worked for two weeks. On another re-build of the VM, the IPA coreos image failed to boot on the system and further 
analysis showed that the IPA image used is that of ‘master’ and not ‘stable/mitaka’. 

This is an attempt to list the things that will be needed to make a solid bifrost stable release which can be used
in a production environment, using a stable release version. Some of the dependencies of bifrost have a 
tagged, branched release for each OpenStack cycle, but some do not. A full-on release will help make bifrost 
much more stable and improve its use in a production environment.

Currently tagged, branched entities.

Bifrost
Ironic
Ironic Python Agent
Ironic Client

Below entities do not have a release branch/tag
Shade
Glean
Diskimage-builder
Coreos IPA Image (Found out we do make a stable-mitaka image, but would be nice to have it as part of the defaults)
Not sure if i am missing anything more.