From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id BC936E00547; Tue, 20 Mar 2018 14:08:16 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 26FFFE00547 for ; Tue, 20 Mar 2018 14:08:15 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Mar 2018 14:08:15 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,337,1517904000"; d="scan'208";a="29759078" Received: from ttorling-mac01.jf.intel.com ([10.24.14.171]) by fmsmga002.fm.intel.com with ESMTP; 20 Mar 2018 14:08:15 -0700 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Tim Orling In-Reply-To: Date: Tue, 20 Mar 2018 14:08:15 -0700 Message-Id: <655551A1-982B-4AF5-BA38-E122543A0DB0@linux.intel.com> References: <833712e4-00aa-1e05-8df5-a0f9a18d4e29@linux.intel.com> <61d1ecb9-e4a6-8d26-9bcc-76c7c42abb7f@linux.intel.com> <1521561579.25754.202.camel@linuxfoundation.org> To: Alexander Kanavin X-Mailer: Apple Mail (2.3273) Cc: "yocto@yoctoproject.org" , "openembedded-core@lists.openembedded.org" Subject: =?UTF-8?B?UmU6IFtPRS1jb3JlXSBZb2N0byBQcm9qZWN0IFN0YXR1cyBXVzEy4oCZMTg=?= X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 21:08:16 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Mar 20, 2018, at 11:00 AM, Alexander Kanavin = wrote: >=20 > 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 weeks... >=20 > My worry is that shorter AUH periods will lead to reminder fatigue. = Also the period between submitting the updates, and having them show up = in master is sometimes less than ideal, even when the freeze is not in = effect. >=20 I agree with both of you. I guess that makes me a transistor that = can=E2=80=99t decide which path to choose :) For meta-perl and meta-python, I am striving to run once a week, but = that isn=E2=80=99t intended to send email out to any maintainers, it is = just for my own accounting. It gets very messy with in-flight patches, = which I hope to fix by using git-pw to not include packages that already = have an upgrade in review. It is also optimistic for me to personally = fix the 20+ packages that need updates at any given moment. This is why = I need run time testing to give me better confidence in auto-upgraded = recipes. Working on it :) > Alex > --=20 > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mail.openembedded.org (Postfix) with ESMTP id A7AC878915 for ; Tue, 20 Mar 2018 21:08:14 +0000 (UTC) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Mar 2018 14:08:15 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,337,1517904000"; d="scan'208";a="29759078" Received: from ttorling-mac01.jf.intel.com ([10.24.14.171]) by fmsmga002.fm.intel.com with ESMTP; 20 Mar 2018 14:08:15 -0700 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) From: Tim Orling In-Reply-To: Date: Tue, 20 Mar 2018 14:08:15 -0700 Message-Id: <655551A1-982B-4AF5-BA38-E122543A0DB0@linux.intel.com> References: <833712e4-00aa-1e05-8df5-a0f9a18d4e29@linux.intel.com> <61d1ecb9-e4a6-8d26-9bcc-76c7c42abb7f@linux.intel.com> <1521561579.25754.202.camel@linuxfoundation.org> To: Alexander Kanavin X-Mailer: Apple Mail (2.3273) Cc: "yocto@yoctoproject.org" , "openembedded-core@lists.openembedded.org" Subject: =?UTF-8?B?UmU6IFt5b2N0b10gWW9jdG8gUHJvamVjdCBTdGF0dXMgV1cxMuKAmTE4?= X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2018 21:08:14 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Mar 20, 2018, at 11:00 AM, Alexander Kanavin = wrote: >=20 > 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 weeks... >=20 > My worry is that shorter AUH periods will lead to reminder fatigue. = Also the period between submitting the updates, and having them show up = in master is sometimes less than ideal, even when the freeze is not in = effect. >=20 I agree with both of you. I guess that makes me a transistor that = can=E2=80=99t decide which path to choose :) For meta-perl and meta-python, I am striving to run once a week, but = that isn=E2=80=99t intended to send email out to any maintainers, it is = just for my own accounting. It gets very messy with in-flight patches, = which I hope to fix by using git-pw to not include packages that already = have an upgrade in review. It is also optimistic for me to personally = fix the 20+ packages that need updates at any given moment. This is why = I need run time testing to give me better confidence in auto-upgraded = recipes. Working on it :) > Alex > --=20 > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core