From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 978ADE00A96; Wed, 21 Mar 2018 07:38:23 -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=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, * medium trust * [192.55.52.120 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id A7535E005A9 for ; Wed, 21 Mar 2018 07:38:21 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Mar 2018 07:38:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,340,1517904000"; d="scan'208";a="44071000" Received: from kanavin-desktop.fi.intel.com (HELO [10.237.68.161]) ([10.237.68.161]) by orsmga002.jf.intel.com with ESMTP; 21 Mar 2018 07:38:19 -0700 To: Philip Balister , "Burton, Ross" References: <833712e4-00aa-1e05-8df5-a0f9a18d4e29@linux.intel.com> <61d1ecb9-e4a6-8d26-9bcc-76c7c42abb7f@linux.intel.com> From: Alexander Kanavin Message-ID: Date: Wed, 21 Mar 2018 16:31:40 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: 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: Wed, 21 Mar 2018 14:38:23 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit 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 doesn't land right in the middle of a >>>     feature freeze. Thoughts? >>> >>> >>> 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. > > Maybe bi-weekly? Could that help reduce the number of upgrades needed > for each run? Only if the maintainers take those reminders as high priority items, and actually send out the patches quickly, and then those patches make it to master. All that needs to happen within those two weeks. Otherwise, the AUH will just re-run the same set. Alex From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by mail.openembedded.org (Postfix) with ESMTP id 9E0AB783E4 for ; Wed, 21 Mar 2018 14:38:19 +0000 (UTC) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Mar 2018 07:38:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,340,1517904000"; d="scan'208";a="44071000" Received: from kanavin-desktop.fi.intel.com (HELO [10.237.68.161]) ([10.237.68.161]) by orsmga002.jf.intel.com with ESMTP; 21 Mar 2018 07:38:19 -0700 To: Philip Balister , "Burton, Ross" References: <833712e4-00aa-1e05-8df5-a0f9a18d4e29@linux.intel.com> <61d1ecb9-e4a6-8d26-9bcc-76c7c42abb7f@linux.intel.com> From: Alexander Kanavin Message-ID: Date: Wed, 21 Mar 2018 16:31:40 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: 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: Wed, 21 Mar 2018 14:38:19 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit 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 doesn't land right in the middle of a >>>     feature freeze. Thoughts? >>> >>> >>> 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. > > Maybe bi-weekly? Could that help reduce the number of upgrades needed > for each run? Only if the maintainers take those reminders as high priority items, and actually send out the patches quickly, and then those patches make it to master. All that needs to happen within those two weeks. Otherwise, the AUH will just re-run the same set. Alex