On Sat, Oct 10, 2015 at 8:07 AM, Boris Bobrov <[email protected]> wrote:

> On Saturday 10 October 2015 08:42:10 Shinobu Kinjo wrote:
> > So what's the procedure?
>
> You go to #openstack-keystone on Friday, choose a bug, talk to someone of
> the
> core reviewers. After talking to them fix the bug.
>

Wash, rinse, repeat? ;)

Looking forward to it, I think this is a much needed pattern!

>
> > Shinobu
> >
> > ----- Original Message -----
> > From: "Adam Young" <[email protected]>
> > To: [email protected]
> > Sent: Saturday, October 10, 2015 12:11:35 PM
> > Subject: Re: [openstack-dev] [keystone] Let's get together and fix all
> the
> > bugs
> >
> > On 10/09/2015 11:04 PM, Chen, Wei D wrote:
> >
> >
> >
> >
> >
> > Great idea! core reviewer’s advice is definitely much important and
> valuable
> > before proposing a fixing. I was always thinking it will help save us if
> we
> > can get some agreement at some point.
> >
> >
> >
> >
> >
> > Best Regards,
> >
> > Dave Chen
> >
> >
> >
> >
> > From: David Stanek [ mailto:[email protected] ]
> > Sent: Saturday, October 10, 2015 3:54 AM
> > To: OpenStack Development Mailing List
> > Subject: [openstack-dev] [keystone] Let's get together and fix all the
> bugs
> >
> >
> >
> >
> >
> > I would like to start running a recurring bug squashing day. The general
> > idea is to get more focus on bugs and stability. You can find the details
> > here: https://etherpad.openstack.org/p/keystone-office-hours Can we
> start
> > with Bug 968696?
>
> --
> С наилучшими пожеланиями,
> Boris
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: [email protected]?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to