Hi Roman, We are doing the same in a bit different way.
Firstly, we are removing package build out of ISO build. These packages will flow the same way we do for MOS components. The will use the same build procedures as all other packages. Secondly, all packages will be put in repository in our mirror. Thirdly, when we start working on new version of MOS, meta information of our mirror will be updated with new release. What does it mean? We'll fork current release to a new one. When package needs an update the developer will be able to produce a new package with updated information. It will pass testing and will be added to mirror though targeted to new release only. If we need to backport it current release it will be back ported using standard procedures. The developer will decide where he needs to bump version to next one and use beta or alpha prefixes in version. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Thu, Mar 26, 2015 at 2:45 AM, Roman Prykhodchenko <m...@romcheg.me> wrote: > Hi folks, > > This end of the release cycle I realized that due to different reasons > bumping a version of Fuel’s components takes much more than just updating a > set of text files. In fact it causes different kinds of cross-component > problems which of course must be fixed. > > This email is not about fixing them but about the way of detecting them > earlier and not delaying any component in the end of release cycles. The > idea is not mine, I borrowed it from one of our folks asked that in a > private channel. I decided to tell that in a public place like this mailing > list is. > > The idea is to bump version in Fuel’s components not in the end of a > release cycle, but in it’s early beginning, i.e., when a stable branch has > been made. What are your thoughts on that? > > > - romcheg > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
