Any thoughts when you want to do a LTS TechForum session. 30th June is now taken and the next scheduled one after that is 14th July. We could try and do a special one on 7th July if that’s better.
I’m reliant on you guys to jointly prepare and present a LTS TF-A Tech forum session
From: Joanna Farley via TF-A firstname.lastname@example.org Date: Monday, 6 June 2022 at 13:47 To: Okash Khawaja email@example.com Cc: Matteo Carlini Matteo.Carlini@arm.com, firstname.lastname@example.org email@example.com Subject: [TF-A] Re: Rebooting LTS discussion Hi Okash,
The next session after next week is Thursday 30th June at 4pm BST. This is also available with nothing currently scheduled.
From: Okash Khawaja firstname.lastname@example.org Date: Monday, 6 June 2022 at 13:34 To: Joanna Farley Joanna.Farley@arm.com Cc: Varun Wadekar email@example.com, Matteo Carlini Matteo.Carlini@arm.com, firstname.lastname@example.org email@example.com Subject: Re: [TF-A] Re: Rebooting LTS discussion Hi Joanna and Varun,
Sounds good to me. I will be out of country during next week. After that should be fine.
On Mon, Jun 6, 2022 at 12:13 PM Joanna Farley <Joanna.Farley@arm.commailto:Joanna.Farley@arm.com> wrote: Varun, Okash, I believe the two of you have some interest in the LTS topic. Would the two of you be willing to jointly prepare and present a TF-A Tech forum session? The next available session is Thursday 16th June at 4pm BST.
I’m sure there are many definitions of what a LTS release branch is in terms of purpose, content, duration etc. I would expect many platform providers are doing this downstream today and I could imagine there may be variations. Some degree of consensus on how this is managed and resourced would be needed I believe between multiple platform providers who would want to consume this.
It would be good to see issues raised for discussion.
I’m happy to host if the two of you and any other platform providers interested can prepare a TF-A session to present to the broader TF-A community.
From: Varun Wadekar via TF-A <firstname.lastname@example.org:email@example.com> Date: Tuesday, 31 May 2022 at 15:23 To: Matteo Carlini <Matteo.Carlini@arm.commailto:Matteo.Carlini@arm.com>, Okash Khawaja <firstname.lastname@example.org:email@example.com>, firstname.lastname@example.org:email@example.com <firstname.lastname@example.org:email@example.com> Subject: [TF-A] Re: Rebooting LTS discussion Hi Matteo/Okash,
Thanks for re-starting the discussion. We (NVIDIA) are still interested in the idea and would like to discuss the next steps. I like the idea of a hotfix release, although would propose back-porting fixes to more tags.
A targeted tech forum or another mechanism works for me. I would like to discuss the scope of the activity and the engagement model.
-----Original Message----- From: Matteo Carlini <Matteo.Carlini@arm.commailto:Matteo.Carlini@arm.com> Sent: Tuesday, 17 May 2022 3:39 PM To: Okash Khawaja <firstname.lastname@example.org:email@example.com>; firstname.lastname@example.org:email@example.com Cc: Varun Wadekar <firstname.lastname@example.org:email@example.com>; firstname.lastname@example.org:email@example.com Subject: RE: [TF-A] Rebooting LTS discussion
External email: Use caution opening links or attachments
Thanks for rebooting the conversation.
Out of the brainstorming from 1.5 yrs ago, we had this page published with an initial RFC proposal for LTSs: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper....
Worth mentioning that, in the meanwhile, the TF-M project has introduced the concept of Hotfix releases (which is a very lightweight process for backporting critical bug fix/security fixes only to the last available tagged release): https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftf-m-user-...
I'm curious to hear others' opinion and interest (@Varun, @Raghu ?) to possibly revive this topic in either in a Tech Forum or at a project TSC/Board level.
-- TF-A mailing list -- firstname.lastname@example.org:email@example.com To unsubscribe send an email to firstname.lastname@example.org:email@example.com