Hi,
To try and minimise trashing of both core reviews and V2.0 patch author(s),
I'd like to propose that we pick a time/day every second week for 3-4
iterations where those interested set aside a set block of time to
collaborate in getting the main rework patches landed. Consider it a set of
mini
Hey Darragh,
I agree with your thought and would like to participate to the reviews,
although the time slots is a little late for me but it works.
Thanks,
Dong Ma (Vincent)
Email: winterma.d...@gmail.com
IRC: larainema
Telephone: +86 18610023880
2016-07-05 0:43 GMT+08:00 Darragh Bai
HI Darragh,
I would like to help where I can in the reviews, but Tuesdays and Thursdays
are my busiest days. I can only guarantee that I am free after 19:00 UTC on
Tuesdays and Thursdays. Monday and Fridays are days where I am free from
summer class obligations but I am not too sure if that will w
On 5 July 2016 at 05:44, Kien Ha wrote:
> HI Darragh,
>
> I would like to help where I can in the reviews, but Tuesdays and
> Thursdays are my busiest days. I can only guarantee that I am free after
> 19:00 UTC on Tuesdays and Thursdays. Monday and Fridays are days where I am
> free from summer c
On Tue, Jul 5, 2016 at 6:32 AM, Darragh Bailey
wrote:
>
>
> On 5 July 2016 at 05:44, Kien Ha wrote:
>
>> HI Darragh,
>>
>> I would like to help where I can in the reviews, but Tuesdays and
>> Thursdays are my busiest days. I can only guarantee that I am free after
>> 19:00 UTC on Tuesdays and Th
It's starting to sound like Friday would suit people best, I'm happy enough
with that day as well, may have to leave slightly before 17hr utc, but
should be able to be present for most of the time.
Darragh Bailey
"Nothing is foolproof to a sufficiently talented fool" - unknown
On 5 Jul 2016 17:21,
Fridays work for me too.
Regards,
Thanh
On 5 July 2016 at 14:03, Darragh Bailey wrote:
> It's starting to sound like Friday would suit people best, I'm happy
> enough with that day as well, may have to leave slightly before 17hr utc,
> but should be able to be present for most of the time.
>
>
Hey Darragh,
For Mon/Fri, the current time slots both works for me.
Thanks,
Dong
>> On Mon, Jul 4, 2016 at 8:47 PM, Dong Ma wrote:
>>
>>> Hey Darragh,
>>>
>>>
>>>
>>> I agree with your thought and would like to participate to the reviews,
>>> although the time slots is a little late for me bu
Sounds like Friday is the clear winner. Do we want to stay this Friday? Or
would everyone prefer a bit more notice to plan things with their other
work?
I'm not around Friday 15th, but it could start then anyway if others are
happy (might need one more core to help land stuff that day)? Otherwise
I am fine with starting this Friday. I am also okay with starting any time
afterwards too.
On Wed, Jul 6, 2016 at 3:14 PM, Darragh Bailey
wrote:
>
> Sounds like Friday is the clear winner. Do we want to stay this Friday? Or
> would everyone prefer a bit more notice to plan things with their othe
On Mon, Jul 04, 2016 at 05:43:14PM +0100, Darragh Bailey wrote:
> Hi,
>
>
> To try and minimise trashing of both core reviews and V2.0 patch author(s),
> I'd like to propose that we pick a time/day every second week for 3-4
> iterations where those interested set aside a set block of time to
> co
This Friday would be perfect for me as it aligns with my team's monthly
"hack day", for which JJB 2.0 collaborative review is perfect.
On Wed, Jul 6, 2016 at 12:20 PM, Kien Ha wrote:
> I am fine with starting this Friday. I am also okay with starting any time
> afterwards too.
>
> On Wed, Jul 6,
Hi,
On 6 Jul 2016 20:26, "Paul Belanger" wrote:
>
Snipped
> > Also thinking that spinning up a temporary public dedicated IRC chat
room
> > would be helpful here, probably look to avoid using one of the existing
> > meeting rooms because I'm assuming that would conflict with other teams,
> > un
Took a bit of doing, but worked out what was needed to use #openstack-sprint
Created an entry on the Virtual Sprint wiki page:
https://wiki.openstack.org/wiki/VirtualSprints#JJB_V2.0_API_Sprint
Chat to you all tomorrow.
On 6 July 2016 at 21:01, Darragh Bailey wrote:
> Hi,
>
> On 6 Jul 2016 20
Hi,
Quick reminder that we're approaching the second planned sync up for JJB
v2.0 api patches.
https://wiki.openstack.org/wiki/VirtualSprints#JJB_V2.0_API_Sprint
https://etherpad.openstack.org/p/jjb_api_v2.0 contains a list of 7 patches
that I'd like us to get close to merging.
The first sync
Hi,
Just realised I forgot to include the date/time in the email (I know it's
available via the virtual sprint wiki page, should have still mentioned it)
Next sprint/sync-up is schedule: 14:00 - 18:00 (UTC) 22nd July
On 20 July 2016 at 12:45, Darragh Bailey wrote:
> Hi,
>
>
> Quick reminder t
On Wed, Jul 20, 2016 at 4:45 AM, Darragh Bailey
wrote:
> Hi,
>
>
> Quick reminder that we're approaching the second planned sync up for JJB
> v2.0 api patches.
> https://wiki.openstack.org/wiki/VirtualSprints#JJB_V2.0_API_Sprint
>
Awesome, thanks for the reminder...I will try to address comments
Hi,
Quick reminder that we're approaching the third planned sync up for JJB v2.0
api patches.
https://wiki.openstack.org/wiki/VirtualSprints#JJB_V2.0_API_Sprint
Time: August 5th 14:00 - 18:00 (UTC) - this friday
Venue: #openstack-meeting (IRC)
Seen some great work in the first two sync-ups with
Hi,
Quick reminder that today is the fourth planned sync up for JJB v2.0 api
patches.
https://wiki.openstack.org/wiki/VirtualSprints#JJB_V2.0_API_Sprint
Time: August 19th 14:00 - 18:00 (UTC) - this friday
Venue: #openstack-meeting (IRC)
Not quite ready to land all of the remaining patches for
Hi Everyone,
I'd like to keep the momentum of JJB 2.0 work going as we're so close to
the finish line. This Friday we're going to continue our sprint in
#openstack-sprint for those who can make it. Wayne suggested we send a
status to the mailing list for those who can't.
To summarize some of the
On Wed, Nov 9, 2016 at 6:41 PM, Thanh Ha
wrote:
> Hi Everyone,
>
> I'd like to keep the momentum of JJB 2.0 work going as we're so close to
> the finish line. This Friday we're going to continue our sprint in
> #openstack-sprint for those who can make it. Wayne suggested we send a
> status to the
On Thu, Nov 10, 2016 at 12:07 PM, Wayne Warren wrote:
> On Wed, Nov 9, 2016 at 6:41 PM, Thanh Ha
> wrote:
>
>> There's 2 patches that need one more core-review to get merged so
>> hopefully someone can take a look at them soon:
>>
>> https://review.openstack.org/336091 Improve logger output for
Hi,
On 11 November 2016 at 14:59, Thanh Ha wrote:
> On Thu, Nov 10, 2016 at 12:07 PM, Wayne Warren wrote:
>
>> On Wed, Nov 9, 2016 at 6:41 PM, Thanh Ha
>> wrote:
>>
>> https://review.openstack.org/358019 Support explicit API and simple
>>> config creation
>>>
>>> There's also some TODO actions
(Starting a second reply for a different patch to make it easier to follow
with threaded mail clients)
I've a comment in
https://review.openstack.org/#/c/319616/8/jenkins_jobs/builder.py that
notes if an application made a call to 'JenkinsManager.update_jobs()' it
would be a reasonable expectation
Think you forgot to Reply-All ;-)
Only spotted that now, while I was waiting for others to chime in and see
different points of view.
On 22 November 2016 at 07:25, Wayne Warren wrote:
>
>
> On Tue, Nov 15, 2016 at 8:04 AM, Darragh Bailey
> wrote:
>
>>
>> So on that patch:
>> https://review.ope
25 matches
Mail list logo
