On Mon, 11 Jul 2022, at 14:42, Bruce Ashfield wrote: > On Mon, Jul 11, 2022 at 9:39 AM Andrei Gherzan <[email protected]> wrote: >> >> On Mon, 11 Jul 2022, at 14:31, Bruce Ashfield wrote: >> > This is new functionality ... and while we don't have a strict rule >> > about not adding new features to existing releases, this is stretching >> > the definition, since it does have the potential to cause issues. >> > >> > It is definitely fine for master, but I'm not particularly keen to >> > start adding new features to kirkstone. >> >> That makes sense. Would you accept it with a disabled default in kirkstone? > > I think that's ok .. it's a balance between keeping kirkstone useful, > and not requiring folks to carry too many changes in their layers. > It's easy enough by inspection to show that the disabled feature won't > impact existing functionality or break anything. > > On further thought, we should keep it disabled by default even in > master, so from that point of view, we can keep them in alignment.
Deal. I'll do this in the next v. Andrei
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#7434): https://lists.yoctoproject.org/g/meta-virtualization/message/7434 Mute This Topic: https://lists.yoctoproject.org/mt/92309185/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
