Skip to content
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

Closed
zandrey opened this issue Mar 10, 2022 · 14 comments
Closed

NXP Release 5.15.5-1.0.0 and Yocto 4.0 Kirkstone #1005

zandrey opened this issue Mar 10, 2022 · 14 comments

Comments

@zandrey
Copy link
Contributor

zandrey commented Mar 10, 2022

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 to kirkstone from master?

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 till 5.15.5-1.0.0 and drop that Kernel branch altogether, replacing it with new one based on prospective 5.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 into kirkstone branch in meta-freescale or it stays with 5.10-2.2.x instead?

Thanks a lot!

-- andrey

@thochstein
Copy link
Contributor

Hi @zandrey, 5.15.5-1.0.0 will release March 31 on honister. The next quarter 5.15.x-2.0.0 will release Jun 30 on kirkstone.

@otavio
Copy link
Member

otavio commented Mar 10, 2022

I'd love to have 5.15-1.0.0 on our kirkstone; @thochstein can we start upstreaming soon?

@zandrey
Copy link
Contributor Author

zandrey commented Mar 10, 2022

Hi @thochstein!

Thanks a lot for such a prompt reply and the information on the dates!

I guess that with 5.15.5-1.0.0 release end of March, it would still give around 4 weeks to upstream it to master in meta-freescale and eventually - to kirkstone. I would then rather give up on the 5.10-2.2.x-imx Kernel and focus on 5.15.y instead.

-- andrey

@thochstein
Copy link
Contributor

I'd love to have 5.15-1.0.0 on our kirkstone; @thochstein can we start upstreaming soon?

Sure, haven't finished moving changes from the last release, mainly gstreamer that I know of.

@nobody93
Copy link

nobody93 commented Apr 28, 2022

There is no kirkstone branch, should we use master to build Kirkstone? Or when are you going to release kirkstone branch?

@otavio
Copy link
Member

otavio commented Apr 28, 2022

For now, yes. We are finishing some more tests before branching but it ought to happen very soon.

@escherstair
Copy link

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).

@otavio otavio changed the title NXP Release 5.15.5-1.0.0 and Yocto 3.5 Kirkstone NXP Release 5.15.5-1.0.0 and Yocto 4.0 Kirkstone May 2, 2022
@otavio
Copy link
Member

otavio commented May 2, 2022

Thanks @escherstair. Updated.

@thochstein what is missing from your side?

@thochstein
Copy link
Contributor

Sorry, I've had other issues to work on and this has slid. I can start upstreaming this week. Is it too late?

@otavio
Copy link
Member

otavio commented May 2, 2022

Please do; we can force it in kirkstone as nobody is using it extensively yet.

@franzflasch
Copy link

Hi @thochstein!

That would be great and would be very appreciated. Any thoughts on how long it will take?

@thochstein
Copy link
Contributor

Hi @franzflasch, I've started on it, hopefully we can get it done in a week or two.

@PierreGrillet
Copy link

Hi guys,

I wonder the state of the kirkstone branch here. As this issue is still opened, is kirkstone ready?

@otavio
Copy link
Member

otavio commented Jul 11, 2022

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.

@otavio otavio closed this as completed Jul 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants