5:55 a.m.
Hello RDO community,
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.
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.
My opinion is that RDO is tracking stable upstream version, so it looks
more like 'only product tweak'. But I wanted to hear also the voice of
community - what you think?
Link to navigation proposal:
https://plus.google.com/115177641540718537778/posts/EEwGmhfDbHB
Thanks
-- Jarda
-------- Original Message --------
Subject: [rhos-dev] Intention for backporting upstream Icehouse feature
to downstream Havana
Date: Mon, 30 Sep 2013 07:51:51 +0200
From: Jaromir Coufal <jcoufal(a)redhat.com>
To: rhos-dev <rh-openstack-dev(a)redhat.com>
CC: pmyers(a)redhat.com, Hugh Brock <hbrock(a)redhat.com>
Hi all,
I've been discussing with Perry and Hugh possibility of backporting some
UI features from upstream Icehouse to our downstream Havana.
Situation is following:
- Currently OpenStack dashboard has vertical navigation
- There are various usability issues
- It is not very close to other RH products
- We are trying to promote horizontal navigation to OpenStack Dashboard
- Currently it is under discussions of design proposal and I am
building static prototype
- We would like to try to get it into upstream master as soon as
possible (beginning of November)
- Benefits of this improvement
- Enhancement of navigation will largely increase UX
- We will get closer to other RH products look & feel
I wanted to confirm also with you, with all above mentioned facts, do
you see backporting this upstream feature into downstream Havana
possible (given the fact that it is in Icehouse upstream by November)?
Can QE test other aspects of OpenStack and focus on UI a bit later so we
can try to add navigation change in?
As long as this is *not* something what could break functionality of
OpenStack - it is just UI enhancement - I hope that it is possible. We
cannot assure that it will pass through community in time, but if we
manage that, I believe it can help RHOS a lot.
Thanks
-- Jarda
6:11 a.m.
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?
Link to navigation proposal:
https://plus.google.com/115177641540718537778/posts/EEwGmhfDbHB
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
6:23 a.m.
On 2013/01/10 13:11, Dave Neary wrote:
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.
If I remember correctly, RHOS 4.0 is
Havana version. Which means the one
which is going to be released as next version.
What is "navigation"?
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.
> 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.
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.
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?
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.
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).
> Link to navigation proposal:
> https://plus.google.com/115177641540718537778/posts/EEwGmhfDbHB
Thanks!
Dave.
Did that help to clarify the situation?
-- Jarda
6:43 a.m.
Hi,
On 10/01/2013 01:23 PM, Jaromir Coufal wrote:
If I remember correctly, RHOS 4.0 is Havana version. Which means the
one
which is going to be released as next version.
Thanks.
> What is "navigation"?
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.
OK - I understand.
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.
I would suggest that it should get into RDO through Icehouse nightlies.
If Red Hat wants to put it in their product without the patches being in
a stable release upstream, then that's up to product management, but I
don't think it should go into RDO if it isn't upstream.
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
6:53 a.m.
On Tue, Oct 1, 2013 at 1:43 PM, Dave Neary <dneary(a)redhat.com> wrote:
I would suggest that it should get into RDO through Icehouse
nightlies.
If Red Hat wants to put it in their product without the patches being in
a stable release upstream, then that's up to product management, but I
don't think it should go into RDO if it isn't upstream.
+1
Also, it would be nice if there'd be a config parameter to switch
between horizontal and vertical layout instead of just replacing one
with the other for good.
-- Sandro
3867
days inactive
3867
days old
4 comments
3 participants
participants (3)
-
Dave Neary -
Jaromir Coufal -
Sandro "red" Mathys