Hi all,
Auto-created bugs could help in this effort. Honestly, nobody can say will
it work or not before we try it.
>From a Horizon's perspective, we need to have some solution which helps us
to know about new features
that would be good to add them to UI in the future. We started with an
On 2018-08-02 14:16:10 -0500 (-0500), Sean McGinnis wrote:
[...]
> Interesting... I hadn't looked into Gerrit functionality enough to know about
> these. Looks like this is probably what you are referring to?
>
> https://gerrit.googlesource.com/plugins/its-storyboard/
Yes, that. Khai Do (zaro)
On Thu, Aug 02, 2018 at 05:56:23PM +, Jeremy Stanley wrote:
> On 2018-08-02 10:09:48 -0500 (-0500), Sean McGinnis wrote:
> [...]
> > I was able to find part of how that is implemented in jeepyb:
> >
> > http://git.openstack.org/cgit/openstack-infra/jeepyb/tree/jeepyb/cmd/notify_impact.py
>
On 2018-08-02 10:09:48 -0500 (-0500), Sean McGinnis wrote:
[...]
> I was able to find part of how that is implemented in jeepyb:
>
> http://git.openstack.org/cgit/openstack-infra/jeepyb/tree/jeepyb/cmd/notify_impact.py
[...]
As for the nuts and bolts here, the script you found is executed
from a
On 8/2/2018 10:59 AM, Radomir Dopieralski wrote:
To be honest, I don't see much point in automatically creating bugs
that nobody is going to look at. When you implement a new feature,
it's up to you to make it available in Horizon and CLI and wherever
else, since the people working there
On Thu, Aug 02, 2018 at 05:59:20PM +0200, Radomir Dopieralski wrote:
> To be honest, I don't see much point in automatically creating bugs that
> nobody is going to look at. When you implement a new feature, it's up to
> you to make it available in Horizon and CLI and wherever else, since the
>
To be honest, I don't see much point in automatically creating bugs that
nobody is going to look at. When you implement a new feature, it's up to
you to make it available in Horizon and CLI and wherever else, since the
people working there simply don't have the time to work on it. Creating a
I'm wondering if someone on the infra team can give me some pointers on how to
approach something, and looking for any general feedback as well.
Background
==
We've had things like the DocImpact tag that could be added to commit messages
that would tie into some automation to create a
