On Tue, 2018-03-20 at 20:00 +0200, Alexander Kanavin wrote:
> On 03/20/2018 05:59 PM, Richard Purdie wrote:
> >
> > >
> > > >
> > > > How long does a single run take, and why not run it every
> > > > month?
> > > Just a bit longer than a day, maybe 30 hours, if it needs to
> > > update
> > > the
Monthly seems like a good enough cadence to give everyone time to review
the mails, send the mails, get reviewed on the list, go through the
autobuilder, and eventually reach master. Too fast and AUH will be sending
nagging mails for a patch which is shortly being merged.
Can we stop bikeshedding
On 03/21/2018 04:24 PM, Philip Balister wrote:
Which brings me to a question: what is a good schedule and cadence
for AUH runs? Currently it's run on the 15th of every odd-numbered
month (so January, March, and so on), but I thought of shifting it
one month forward, so it does
On 03/20/2018 05:26 AM, Alexander Kanavin wrote:
> On 03/20/2018 12:52 PM, Burton, Ross wrote:
>> Which brings me to a question: what is a good schedule and cadence
>> for AUH runs? Currently it's run on the 15th of every odd-numbered
>> month (so January, March, and so on), but I thoug
> On Mar 20, 2018, at 11:00 AM, Alexander Kanavin
> wrote:
>
> On 03/20/2018 05:59 PM, Richard Purdie wrote:
How long does a single run take, and why not run it every month?
>>> Just a bit longer than a day, maybe 30 hours, if it needs to update
>>> the
>>> typical amount of 100-150 packag
On 03/20/2018 05:59 PM, Richard Purdie wrote:
How long does a single run take, and why not run it every month?
Just a bit longer than a day, maybe 30 hours, if it needs to update
the
typical amount of 100-150 packages. I'll shift it to monthly then.
Personally I'm leaning to every couple of we
On Tue, 2018-03-20 at 13:26 +0200, Alexander Kanavin wrote:
> On 03/20/2018 12:52 PM, Burton, Ross wrote:
> >
> > Which brings me to a question: what is a good schedule and
> > cadence
> > for AUH runs? Currently it's run on the 15th of every odd-
> > numbered
> > month (so January, Ma
On 03/20/2018 12:52 PM, Burton, Ross wrote:
Which brings me to a question: what is a good schedule and cadence
for AUH runs? Currently it's run on the 15th of every odd-numbered
month (so January, March, and so on), but I thought of shifting it
one month forward, so it doesn't lan
On 20 March 2018 at 10:07, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> On 03/19/2018 10:07 PM, Burton, Ross wrote:
>
>> Do we have a place identified for new changes (2.6) while 2.5
>> stabilizes.
>>
>>
>> A formal place, no. I tend to queue stuff in a branch if master
On 03/19/2018 10:07 PM, Burton, Ross wrote:
Do we have a place identified for new changes (2.6) while 2.5
stabilizes.
A formal place, no. I tend to queue stuff in a branch if master isn't
taking all of my energy, otherwise the patches will sit on the list
until 2.5 releases. Typical
On 19 March 2018 at 19:22, akuster808 wrote:
> YP 2.5 M3 is in feature freeze. See status above.
>
> Does this include package updates?
>
Yes, upgrades count as features.
> Do we have a place identified for new changes (2.6) while 2.5 stabilizes.
>
A formal place, no. I tend to queue stuff
On 03/19/2018 08:45 AM, Jordan, Robin L wrote:
>
> Current Dev Position: YP 2.5 M3 final close out.
>
> Next Deadline: YP 2.5 M3 cut off was 2/19/18
>
> *** FEATURE FREEZE for 2.5 has passed ***
>
>
>
> SWAT lead is currently Ross.
>
> SWAT team rotation: Armin -> Ross on March 23, 2018
>
> SWA
12 matches
Mail list logo
