v@lists.openstack.org>"
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, May 18, 2017 at 11:40 AM
To:
"openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-
e: Thursday, May 18, 2017 at 11:40 AM
> To: "openstack-dev@lists.openstack.org"
> Subject: Re: [openstack-dev] [horizon] Blueprint process question
>
>
>
> There isn't a specific time for blueprint review at the moment. It's usually
> whenever I get time,
k.org"
Subject: Re: [openstack-dev] [horizon] Blueprint process question
There isn't a specific time for blueprint review at the moment. It's usually
whenever I get time, or someone asks via email or IRC. During the weekly
meetings we always have time for open discussion of bugs/bl
There isn't a specific time for blueprint review at the moment. It's usually
whenever I get time, or someone asks via email or IRC. During the weekly
meetings we always have time for open discussion of bugs/blueprints/patches etc.
Rob
On 18 May 2017 at 16:31, Waines, Greg
mailto:greg.wai...@wi
A blueprint question for horizon team.
I registered a new blueprint the other day.
https://blueprints.launchpad.net/horizon/+spec/vitrage-alarm-counts-in-topnavbar
Do I need to do anything else to get this reviewed? I don’t think so, but
wanted to double check.
How frequently do horizon bluepri
