Re: [bitbake-devel] End of whinlatter stable support
Martin Jansa <[email protected]> Fri, 3 Apr 2026 11:14:57 +0200
| Newsgroups | org.yoctoproject.lists.yocto,org.openembedded.lists.bitbake-devel,org.openembedded.lists.openembedded-core |
|---|---|
| Message-ID | <CA+chaQdp8E_HMyo6Qx6C+PuRrLbrqgbFdQF_WdbZS1ONncxb3w@mail.gmail.com> |
On Fri, Apr 3, 2026 at 10:46 AM Yoann Congal via lists.openembedded.org <[email protected]> wrote: > > Hello everyone, > > As you may have noticed, the end-of-life date of whinlatter (2.16 for > bitbake) is near. > The last release of whinlatter will be the 5.3.4 and will be built in > the week of the 20th of april 2026 for a release the week of the 6th of may. > > If you have patches that you want to see merged in this last version, > please send them before the 10th (next week) so we get enough time for > review and testing. I would like to see my glibc-2.43 compatibility changes I've sent last week merged. I've tested it on 26.04 in docker, if it doesn't show any issue on other hosts used by AB, then what's the harm of merging them to whinlatter and scarthgap? Even after whinlatter gets EOL someone might use latest ubuntu release on host and then try to compare his wrynose build (where 26.04 works fine) with whinlatter build (which fails immediately without these changes). I often use EOL OE releases when trying to "bisect" what changed in upstream layers e.g. between scarthgap and wrynose. Cheers,