You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Andrew Bayer <an...@gmail.com> on 2011/08/15 20:05:12 UTC
RTC process/policy discussion
So we've settled on RTC. Now the question is what the process/policy will
be. I'd tend to go with the most lightweight we can get - a 72 hour window
for voting? Does that sound reasonable? Do we need more than one +1 to
approve something?
A.
Re: RTC process/policy discussion
Posted by Andrew Bayer <an...@gmail.com>.
Sounds good! Thanks!
A.
On Mon, Aug 15, 2011 at 11:54 AM, John Sichi <js...@fb.com> wrote:
> I'm going to be leaving on vacation in a couple of days (back Aug 29); if
> you want, I'll send email to get it going now.
>
> JVS
>
> On Aug 15, 2011, at 11:32 AM, Andrew Bayer wrote:
>
> > Actually, I can probably help with them as well - they're hosting a big
> > chunk of the Jenkins project infrastructure. That definitely sounds worth
> > pursuing - who wants to open up a dialogue? =)
> >
> > A.
> >
> > On Mon, Aug 15, 2011 at 11:27 AM, John Sichi <js...@fb.com> wrote:
> >
> >> If it's useful, I can help with getting VM's allocated here:
> >>
> >> http://supercell.osuosl.org/about
> >>
> >> I've been meaning to get it going for Hive patch testing but haven't
> gotten
> >> around to it.
> >>
> >> The OSUOSL folks are very responsive and can probably help with adding
> >> support for more OS's as needed.
> >>
> >> JVS
> >>
> >> On Aug 15, 2011, at 11:19 AM, Roman Shaposhnik wrote:
> >>
> >>> On Mon, Aug 15, 2011 at 11:14 AM, Andrew Bayer <andrew.bayer@gmail.com
> >
> >> wrote:
> >>>> Yeah, I would too, but first we need functional build boxes. =) Once
> >> we've
> >>>> got those and a functioning build, I'll bang out the patch build.
> >>>
> >>> Having boxes as part of Apache infra would be quite nice. Andre and I
> >>> are working
> >>> on that right now so that we can have a public-facing Jenkins
> >>> available. However,
> >>> for the testpatch we don't really have to have boxes available in the
> >> open.
> >>>
> >>> Perhaps we can find somebody to donate cycles on the boxes behind the
> >> firewall.
> >>> I think it'll be as effective.
> >>>
> >>> Thanks,
> >>> Roman.
> >>
> >>
>
>
Re: RTC process/policy discussion
Posted by John Sichi <js...@fb.com>.
I'm going to be leaving on vacation in a couple of days (back Aug 29); if you want, I'll send email to get it going now.
JVS
On Aug 15, 2011, at 11:32 AM, Andrew Bayer wrote:
> Actually, I can probably help with them as well - they're hosting a big
> chunk of the Jenkins project infrastructure. That definitely sounds worth
> pursuing - who wants to open up a dialogue? =)
>
> A.
>
> On Mon, Aug 15, 2011 at 11:27 AM, John Sichi <js...@fb.com> wrote:
>
>> If it's useful, I can help with getting VM's allocated here:
>>
>> http://supercell.osuosl.org/about
>>
>> I've been meaning to get it going for Hive patch testing but haven't gotten
>> around to it.
>>
>> The OSUOSL folks are very responsive and can probably help with adding
>> support for more OS's as needed.
>>
>> JVS
>>
>> On Aug 15, 2011, at 11:19 AM, Roman Shaposhnik wrote:
>>
>>> On Mon, Aug 15, 2011 at 11:14 AM, Andrew Bayer <an...@gmail.com>
>> wrote:
>>>> Yeah, I would too, but first we need functional build boxes. =) Once
>> we've
>>>> got those and a functioning build, I'll bang out the patch build.
>>>
>>> Having boxes as part of Apache infra would be quite nice. Andre and I
>>> are working
>>> on that right now so that we can have a public-facing Jenkins
>>> available. However,
>>> for the testpatch we don't really have to have boxes available in the
>> open.
>>>
>>> Perhaps we can find somebody to donate cycles on the boxes behind the
>> firewall.
>>> I think it'll be as effective.
>>>
>>> Thanks,
>>> Roman.
>>
>>
Re: RTC process/policy discussion
Posted by Andrew Bayer <an...@gmail.com>.
Actually, I can probably help with them as well - they're hosting a big
chunk of the Jenkins project infrastructure. That definitely sounds worth
pursuing - who wants to open up a dialogue? =)
A.
On Mon, Aug 15, 2011 at 11:27 AM, John Sichi <js...@fb.com> wrote:
> If it's useful, I can help with getting VM's allocated here:
>
> http://supercell.osuosl.org/about
>
> I've been meaning to get it going for Hive patch testing but haven't gotten
> around to it.
>
> The OSUOSL folks are very responsive and can probably help with adding
> support for more OS's as needed.
>
> JVS
>
> On Aug 15, 2011, at 11:19 AM, Roman Shaposhnik wrote:
>
> > On Mon, Aug 15, 2011 at 11:14 AM, Andrew Bayer <an...@gmail.com>
> wrote:
> >> Yeah, I would too, but first we need functional build boxes. =) Once
> we've
> >> got those and a functioning build, I'll bang out the patch build.
> >
> > Having boxes as part of Apache infra would be quite nice. Andre and I
> > are working
> > on that right now so that we can have a public-facing Jenkins
> > available. However,
> > for the testpatch we don't really have to have boxes available in the
> open.
> >
> > Perhaps we can find somebody to donate cycles on the boxes behind the
> firewall.
> > I think it'll be as effective.
> >
> > Thanks,
> > Roman.
>
>
Re: RTC process/policy discussion
Posted by John Sichi <js...@fb.com>.
If it's useful, I can help with getting VM's allocated here:
http://supercell.osuosl.org/about
I've been meaning to get it going for Hive patch testing but haven't gotten around to it.
The OSUOSL folks are very responsive and can probably help with adding support for more OS's as needed.
JVS
On Aug 15, 2011, at 11:19 AM, Roman Shaposhnik wrote:
> On Mon, Aug 15, 2011 at 11:14 AM, Andrew Bayer <an...@gmail.com> wrote:
>> Yeah, I would too, but first we need functional build boxes. =) Once we've
>> got those and a functioning build, I'll bang out the patch build.
>
> Having boxes as part of Apache infra would be quite nice. Andre and I
> are working
> on that right now so that we can have a public-facing Jenkins
> available. However,
> for the testpatch we don't really have to have boxes available in the open.
>
> Perhaps we can find somebody to donate cycles on the boxes behind the firewall.
> I think it'll be as effective.
>
> Thanks,
> Roman.
Re: RTC process/policy discussion
Posted by Roman Shaposhnik <rv...@apache.org>.
On Mon, Aug 15, 2011 at 11:14 AM, Andrew Bayer <an...@gmail.com> wrote:
> Yeah, I would too, but first we need functional build boxes. =) Once we've
> got those and a functioning build, I'll bang out the patch build.
Having boxes as part of Apache infra would be quite nice. Andre and I
are working
on that right now so that we can have a public-facing Jenkins
available. However,
for the testpatch we don't really have to have boxes available in the open.
Perhaps we can find somebody to donate cycles on the boxes behind the firewall.
I think it'll be as effective.
Thanks,
Roman.
Re: RTC process/policy discussion
Posted by Andrew Bayer <an...@gmail.com>.
Yeah, I would too, but first we need functional build boxes. =) Once we've
got those and a functioning build, I'll bang out the patch build.
A.
On Mon, Aug 15, 2011 at 11:07 AM, Roman Shaposhnik <rv...@apache.org> wrote:
> On Mon, Aug 15, 2011 at 11:05 AM, Andrew Bayer <an...@gmail.com>
> wrote:
> > So we've settled on RTC. Now the question is what the process/policy will
> > be. I'd tend to go with the most lightweight we can get - a 72 hour
> window
> > for voting? Does that sound reasonable? Do we need more than one +1 to
> > approve something?
>
> I'd go with 72 hours and just a single +1. I also would like to have a
> testpatch-like
> process in place so that submitted patches can be automatically vetted
> on at least
> CentOS/Ubuntu (would be really nice to also include OpenSUSE/Debian).
>
> Thanks,
> Roman.
>
Re: RTC process/policy discussion
Posted by Roman Shaposhnik <rv...@apache.org>.
On Mon, Aug 15, 2011 at 11:05 AM, Andrew Bayer <an...@gmail.com> wrote:
> So we've settled on RTC. Now the question is what the process/policy will
> be. I'd tend to go with the most lightweight we can get - a 72 hour window
> for voting? Does that sound reasonable? Do we need more than one +1 to
> approve something?
I'd go with 72 hours and just a single +1. I also would like to have a
testpatch-like
process in place so that submitted patches can be automatically vetted
on at least
CentOS/Ubuntu (would be really nice to also include OpenSUSE/Debian).
Thanks,
Roman.