Received: from mail-qt1-f193.google.com (mail-qt1-f193.google.com [209.85.160.193]) by mx.groups.io with SMTP id smtpd.web10.33465.1591632211579065255 for ; Mon, 08 Jun 2020 09:03:31 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@kudzu-us.20150623.gappssmtp.com header.s=20150623 header.b=utXPpCAD; spf=none, err=permanent DNS error (domain: kudzu.us, ip: 209.85.160.193, mailfrom: jdmason@kudzu.us) Received: by mail-qt1-f193.google.com with SMTP id i16so15051876qtr.7 for ; Mon, 08 Jun 2020 09:03:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kudzu-us.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Q496hhnp4BiaAmNPMw0L3iYv4xuVPTXV7MokFYrCMRE=; b=utXPpCADy/bCHKtH6no6Pk8GUO/+QtQ2Sl7q7noNT0/EPzL5Zl/JRcaULK2+n/q5CM F7lvZIyMxRqKol3L4n4M8yY7O7ZDNIop2I+bcMGtRw0WTlZC6sIrKXgP3dv0p06+uDJJ uR7uOFtzrjkJoYTcvAhc6yZgywlHH3p3LpDv4LBEjnuVoRcRZ2HJoDGqfwcoKud/qn+P Acc0bzNg1bB88+49TduP7OuweghQr0aAZaqe5lLQ7yebKQlDccAYrOhaU9CjZRaYCCOB m6i+XIAlJKYjLGqPgPb5veubfvtjK7NVjSVhR2q8EEA/LeD2ubvvhQnGuHTBaN6nWfcB QjHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Q496hhnp4BiaAmNPMw0L3iYv4xuVPTXV7MokFYrCMRE=; b=sr9aVrIYQAmYcH2knXp5pGel5jKjNbzdZk0p5T6xXaRBitVmx98STbtzKyP3q/v/Dq gweSiTMMbAce83fKptF5ZW9+rRIWVLXPuafWhkfBHRaop6suzttvUWWwfSSiChqOmQSi /eWmkdYYsy7CFXXxxus1q938pECRDpGl1wyWgnqipSpSSHWap4Tr6nqZGTV8wRdHKm5l iH/3cjMxDnZNj21iiieKfsNtUv6xenPNOWWzQ2RBN3W50oXiVQxd/T5gVZ6VDOS0/b6S nxZ/Igrfggb4gJq+f9ecBm3LndlF+L3B6DL+Xwj2ADn8EFnAcEi2YoCN1zwBYUBF8Unf jAuA== X-Gm-Message-State: AOAM532UY+VhqLVjPARHpHFVQTdEpJL24q/9Q0KPlt7xDiiKOKzpc9P9 sYx1xSTrsI9YxW/nbs6xKXQ4SA== X-Google-Smtp-Source: ABdhPJyVmvlQTGlMqG2hFXwVJy+KasfS4bENc1YiUYMRmQ/TcjWVzok6gEZySQFVkS46EeE1sLLH3Q== X-Received: by 2002:ac8:192c:: with SMTP id t41mr22718634qtj.32.1591632210634; Mon, 08 Jun 2020 09:03:30 -0700 (PDT) Return-Path: Received: from kudzu.us ([2605:a601:a61a:4700:b9b3:35e6:b1bd:2c87]) by smtp.gmail.com with ESMTPSA id f30sm7882279qtb.9.2020.06.08.09.03.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 08 Jun 2020 09:03:29 -0700 (PDT) Date: Mon, 8 Jun 2020 12:03:28 -0400 From: "Jon Mason" To: Denys Dmytriyenko Cc: Nicolas Dechesne , Joshua Watt , Bertrand Marquis , meta-arm@lists.yoctoproject.org Subject: Re: [meta-arm][PATCH] meta-arm: Remove meta-python dependency Message-ID: <20200608160327.GG15959@kudzu.us> References: <20200529151427.20272-1-JPEWhacker@gmail.com> <90DD68A5-0834-4C82-8A06-BC3972756CA3@arm.com> <6d6ccf5c-f134-1a15-e5eb-8f5e10d03832@gmail.com> <09986319-6338-471F-A0C1-5096F5ED7AA3@arm.com> <20200601213141.GA31505@kudzu.us> <20200601225610.GD31505@kudzu.us> <20200605234454.GQ17660@denix.org> MIME-Version: 1.0 In-Reply-To: <20200605234454.GQ17660@denix.org> User-Agent: Mutt/1.10.1 (2018-07-13) Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jun 05, 2020 at 07:44:54PM -0400, Denys Dmytriyenko wrote: > On Tue, Jun 02, 2020 at 08:10:04AM +0200, Nicolas Dechesne wrote: > > hey Jon, > > > > > > Hmm, that's really unfortunate. That makes me think this layer is not > > > > actually intended to be a centralized location for ARM related things, > > > and > > > > I'm probably not going to try and consolidate things from other layers > > > here > > > > anymore. Not having a master branch that can be used with the master > > > branch > > > > of OE-core really eliminates the possibility for me to use a BSP layer > > > like > > > > e.g. meta-rockchip for upstream development and testing if that BSP layer > > > > depends on meta-arm and meta-arm is perpetually stuck on the last > > > release. > > > > > > I'm in no way saying that meta-arm master should not work with > > > upstream master. I'm saying that we want to keep compatability with > > > the previous release so that we can cut stable releases for customers. > > > > > > > I have been very supportive about meta-arm as the central location for ARM > > pieces, and still believe it's the right thing to do. But like Joshua, I > > find this discussion a bit disappointing. A layer is a "social contract" > > between the community behind this layer, and the rest of the OE/YP > > community. Refusing proper and meaningful community patches in master > > because it doesn't some 'internal' needs doesn't feel right. > > > > > > > We have a requirement to release BSP SW based on YP. Just like I > > > would expect other vendors/people who want to use meta-arm. So, there > > > are a few ways we can approach this issue. > > > > > > 1. Merge patches onto dunfell branch > > > 2. A development branch based on dunfell > > > 3. Use master meta-arm-bsp and dunfell branches for meta-arm and > > > meta-arm-toolchain > > > 4. Keep master compatible with dunfell > > > > > > > I think the mistake we made (I am saying we, since I was involved in that > > discussion) is to have a single tree that includes both the 'community' > > content that the ARM ecosystem wants to depend on and the specific ARM > > "products" that are needed by very few specific people (e.g. your BSP > > product). > > > > I think #3 is the most sensible choice, e.g. you need to split meta-arm > > into 'community' pieces (I think that would correspond to meta-arm and > > meta-arm-toolchain layers) and your product pieces. When we build your > > product with OE, you would reply on the 'community' meta-arm, and if any > > hack or custom integration is needed, then you can do that in your product > > tree. You might even overlay things for some time there, it's fine for a > > product layer. Of course you will need to worry about doing the 'proper' > > fix into the community meta-arm at some point. But if you don't commit to > > maintaining a layer for the ARM community, the risk is that everyone will > > start forking meta-arm recipes, which is not what we want. > > After giving it some thought for couple days, I tend to agree with Nico that > it may be better off to split out meta-arm-bsp away from the rest of meta-arm > repository to allow it to make releases against any YP versions and branches. > > > > > One is simple, we actually do our development on the dunfell branch. > > > However, this breaks it from being a stable branch. So, this is a > > > non-starter > > > > > > > Two is still simple, we do all of our internal development on a second > > > dunfell branch ("dunfell-dev") and make any releases we have off of > > > that. The problem with this is the integration and testing. If there > > > are multiple branches to test, can we expect developers to test every > > > combination? Also, there might be a need for different versions of > > > the patches depending on how much master and dunfell-dev diverge. > > > > > > > That is an alternate variant of splitting the trees.. doing your 'product' > > in a product branch, and keep the expected branches (dunfell, master, ...) > > as community branches. It really depends if meta-arm-bsp is really expected > > to be a community thing ever, or if it's your product only. In which case > > it might be more appropriate to split it apart. > > > > > > > > > > Three is more complex. Since only meta-arm-bsp needs releases, we can > > > simply let that one float and fix the others on the stable branches. > > > The problem with this is that we are currently needing to add recipes > > > for things into meta-arm that others might need (like SCP, EDK2, etc). > > > So, this will work once we have more stability in meta-arm, but right > > > now we are adding too much stuff to make it viable for the next > > > release. > > > > > > Four is simple, we keep compatability with dunfell and make the > > > releases off of that. The potential hazard with this is if something > > > in YP master requires that compatability to be broken. > > > > > > > I presonally would like #4, because it is simple. However, if this > > > will prevent others from using meta-arm, then let's have a discussion > > > on it. Perhaps I am not understanding something fundamental. > > > > > > > But the whole discussion started because you said you needed to keep master > > compatible with dunfell. Even though as you said, it might fail eventually. I would appreciate it if everyone could take a look at the email I sent out on Friday, "Proposal for the branching policy of meta-arm". https://lists.yoctoproject.org/g/meta-arm/message/557 Creating and maintaining an active community around meta-arm is our #1 priority. We had extensive discussions internally, and came up with this proposal. I believe it addresses the issues everyone had, and should prevent this kind of thing from happening in the future. This is a proposal and not a dictate. So, please post comments and questions to that thread. Thanks, Jon