[oe] [meta-networking][PATCH] inetutils: 1.9.2 -> 1.9.4

[Khem Raj]

> On Aug 17, 2015, at 2:13 PM, Randy MacLeod <randy.macleod at windriver.com> wrote:
> 
> On 2015-08-17 11:03 AM, Joe MacDonald wrote:
>> [Re: [oe] [meta-networking][PATCH] inetutils: 1.9.2 -> 1.9.4] On 15.08.17 (Mon 14:05) Kang Kai wrote:
>> 
>>> On 2015年08月12日 10:05, kai.kang at windriver.com wrote:
>>>> From: Kai Kang <kai.kang at windriver.com>
>>>> 
>>>> Upgrade inetutils from 1.9.2 to 1.9.4.
>>> 
>>> Ping?
>> 
>> Since I'm seeing a lot of these lately I thought I might explain my
>> current workflow.
> 
> Thanks for the background.
> 
>> For build or security issues, I'm trying to stay on
>> top of them and be as responsive as possible,
> 
> okay.
> 
>> but for general recipe
>> updates, particularly ones like this where the log shows essentially
>> nothing critical has changed, I'm holding off until at least my
>> autobuilders get to chew on them and reassure me we're not bringing in
>> new QA (or worse) issues,
> 
> I'd hope that means a day or two and not a week, right?

its about a week. Reason is the machines capacity/power vs. number of recipes to build.

> 
>> and ideally I prefer to see a pass in one of
>> Martin's "state of the world" builds.
> 
> I assumed that the state-of-the-world builds would be for master
> and the release branches but no:
>   http://www.openembedded.org/wiki/Bitbake_World_Status_Setup
> 
>   "It's not using "master" branches,
>     but "jansa/master" branches in ..."
> 
> They appear to happen every day:
>   http://logs.nslu2-linux.org/buildlogs/oe/world/
> And the stats are published once or twice a week, most of the time...
>   http://www.openembedded.org/wiki/Bitbake_World_Status
> 
> Hmmm, would newer build systems be useful:
>   "Usually I build for 3 MACHINE qemuarm, qemux86, qemux86-64.
>    Each MACHINE takes about 20-24hours so sometimes there is
>    bigger delay."
> 
>> I also try to give everyone on
>> the list a reasonable amount of time to respond to anything as well, but
>> that's not a gating factor.
> 
> What's a reasonable time? ~ 1-2 days?
> 
> Just trying ensure that our ping time is reasonable. :)


Wait for a week at-least.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20150817/9fa38c06/attachment-0002.sig>