<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#333333">
<br>
<div class="moz-cite-prefix">On 2013/01/10 13:11, Dave Neary wrote:<br>
</div>
<blockquote cite="mid:524AADE2.1080307@redhat.com" type="cite">
<pre wrap="">Hi Jaromir,
On 10/01/2013 12:55 PM, Jaromir Coufal wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">
Just to clarify - RHOS 4.0 is Red Hat OpenStack Grizzly version? I am
not familiar with the product versioning.</pre>
</blockquote>
If I remember correctly, RHOS 4.0 is Havana version. Which means the
one which is going to be released as next version.<br>
<br>
<blockquote cite="mid:524AADE2.1080307@redhat.com" type="cite">
<pre wrap="">What is "navigation"?</pre>
</blockquote>
It is UI change - going from vertical to horizontal layout. So it
means HTML, CSS and JS changes in OpenStack Dashboard. We are not
changing information architecture. Just look&feel.<br>
<br>
<blockquote cite="mid:524AADE2.1080307@redhat.com" type="cite">
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap="">
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.</pre>
</blockquote>
The goal is to get this enhancement into following RHOS release. So
the question is if it has to go through RDO first or we can just
consider it as 'product only' and get it to RDO at the time when it
is merged upstream.<br>
<br>
<blockquote cite="mid:524AADE2.1080307@redhat.com" type="cite">
<pre wrap="">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?</pre>
</blockquote>
Yes, but it won't be backported into upstream Havana. From the
upstream point of view, the feature will be available only in
Icehouse. What is the intention is to get this important change to
our customers as soon as possible.<br>
<br>
It means, if we make this happen, downstream Havana release would
deffer a bit from upstream Havana release (because of the navigation
and branding of course).<br>
<br>
<blockquote cite="mid:524AADE2.1080307@redhat.com" type="cite">
<blockquote type="cite">
<pre wrap="">Link to navigation proposal:
<a class="moz-txt-link-freetext" href="https://plus.google.com/115177641540718537778/posts/EEwGmhfDbHB">https://plus.google.com/115177641540718537778/posts/EEwGmhfDbHB</a>
</pre>
</blockquote>
<pre wrap="">
Thanks!
Dave.
</pre>
</blockquote>
<br>
Did that help to clarify the situation?<br>
-- Jarda<br>
</body>
</html>