On Tue, 27 Sept 2022 at 18:06, Peter Kjellerstedt <[email protected]> wrote: > I (and the small team I am part of) is the proxy between them and Yocto. > Thus I try to address their needs by making sure new versions of Yocto > continues to work for them without having 500+ developers facing the > same problems. I.e., it is my job to work with upstream, which is what > I am trying to do here.
Excuse me, but your job is not to 'work with upstream'. Your job is to make damn sure 'upstream' continues to exist. Which means: go to your management, describe the situation we're in (you have the numbers), and ask that they allocate at least one developer to work in upstream full time. Not drive-by patches to fix your specific product problems, but upstream proper: something that makes the project sustainable, e.g. fixing medium+/high bugs, working on new features, upgrading recipes, sending pending patches upstream. This works never ends, and no one wants to do it. If you can do this, I promise to be more sympathetic to your particular issues, but as things stand, it's rather difficult. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171114): https://lists.openembedded.org/g/openembedded-core/message/171114 Mute This Topic: https://lists.openembedded.org/mt/93847437/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
