Hi Jaromir,
On 10/01/2013 12:55 PM, Jaromir Coufal wrote:
I am forwarding mail about backporting navigation change to RHOS 4.0.
It
has huge impact on OS users, more is explained in forwarded e-mail.
Just to clarify - RHOS 4.0 is Red Hat OpenStack Grizzly version? I am
not familiar with the product versioning.
What is "navigation"?
Situation is, that we might not be able to get navigation into
upstream/master in very short timeframe (1-2 weeks). Question then is,
if it makes sense to include the change in RDO first and then to RHOS
(even if upstream/master might adapt it later and in a bit *different*
form), or if it should be considered only RHOS business and RDO will
adapt it once it is merged to upstream master.
RDO packages what is shipped by upstream OpenStack - if you are
proposing putting a change into Red Hat OpenStack as a path to getting
it into RDO, that won't work. The usual path to getting something into
RDO is to propose a patch upstream to OpenStack.
Also, you mention that this is a change to the UI in Icehouse which you
want to backport to Havana, a change which is too significant to make it
into Havana before release. I don't think it's good to have features
present in RDO Havana which are not yet committed upstream. Perhaps the
patch would be accepted into the stable Havana branch, in which case it
would be in RDO packages as soon as OpenStack 2013.1.1 is released?
Thanks!
Dave.
--
Dave Neary - Community Action and Impact
Open Source and Standards, Red Hat -
http://community.redhat.com
Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13