-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NXP Release 5.15.5-1.0.0 and Yocto 4.0 Kirkstone #1005
Comments
Hi @zandrey, |
I'd love to have 5.15-1.0.0 on our kirkstone; @thochstein can we start upstreaming soon? |
Hi @thochstein! Thanks a lot for such a prompt reply and the information on the dates! I guess that with -- andrey |
Sure, haven't finished moving changes from the last release, mainly gstreamer that I know of. |
There is no kirkstone branch, should we use master to build Kirkstone? Or when are you going to release kirkstone branch? |
For now, yes. We are finishing some more tests before branching but it ought to happen very soon. |
Based on what I see here Yocto Kirkstone number has been switched to 4.0 (no more 3.5 as it was before, and as it is in the title of this issue). |
Thanks @escherstair. Updated. @thochstein what is missing from your side? |
Sorry, I've had other issues to work on and this has slid. I can start upstreaming this week. Is it too late? |
Please do; we can force it in kirkstone as nobody is using it extensively yet. |
Hi @thochstein! That would be great and would be very appreciated. Any thoughts on how long it will take? |
Hi @franzflasch, I've started on it, hopefully we can get it done in a week or two. |
Hi guys, I wonder the state of the kirkstone branch here. As this issue is still opened, is kirkstone ready? |
We have it all in sync with master and it looks good, AFAIK. Please give it a go. I'll close this to avoid confusing users. |
Recent status published by Yocto Project sets the next LTS 3.5 Kirkstone release date to
2022/04/29
I've seen some mentions that there is an upcoming release planned from NXP (
5.15.5-1.0.0
) and wanted to check if it is planned to be included in the meta-freescale that would branch out tokirkstone
frommaster
?One reason being (among all others) is that I'm holding the Kernel branch
5.10-2.2.x-imx
for linux-fslc-imx in my fork, and currently I have either the option to submit it to this layer, pick it up and got with it in Kirkstone, or wait till5.15.5-1.0.0
and drop that Kernel branch altogether, replacing it with new one based on prospective5.15.5-1.0.0
.Another reason for this curiosity from my side would be that if the next NXP Release comes out close to the Kirkstone - it might be too late to merge a lot of changes into the LTS release, while if it is imminent - then there would still be time to pick it up and have a "stabilization window" till the end of April.
@thochstein
Do you have any information or prospective date when the next NXP
5.15.5-1.0.0
comes out?@otavio
Should the next NXP
5.15.5-1.0.0
be considered to be integrated intokirkstone
branch in meta-freescale or it stays with5.10-2.2.x
instead?Thanks a lot!
-- andrey
The text was updated successfully, but these errors were encountered: