The Yocto project has declared a Yocto LTS version for version 3.1 coming out in April. They also announced that YP 3.0 (Zeus branch) will only be supported through June, 2020.  The current AGL plan of record is to use YP 3.0 (Zeus) for Jumping Jellyfish (planned release July 2020) and Kooky Koi (planned release February 2021).  Assuming KK’s life-span is at least 6 months after release into 2021 we would have people using an unsupported version of the YP for one year or longer. This information was reviewed with the AGL Steering Committee on March 12, who referred the matter to the SAT to determine the plan going forward. 
 
 
Given the above information the SAT debated the timing of switching to YP 3.1 and how long the project should continue to use YP 3.1.  #
Based on experience in past years when we upgraded to every YP release, JJ would be delayed to September if we switch to YP 3.1. if we switch for JJ. 

1. 
   Feeling was that waiting to KK to upgrade might result in a lot of throwaway work for JJ. 
2. 
   Biggest issue is BSPs and their availability.  While we can assume that RPI, Intel, and BeagleBone Enhanced will be ready on day 1 of 3.1 release we will not have a Renesas BSP available. 
3. 
   Userland: Can we keep multimedia packages(e.g. Weston, gstreamer) and other version as older versions in first 3.1 up rev and then wait for the BSPs to update? The feeling on the call is that this is possible. 

 
Renesas BSP availability  *
Kurokawa-san showed an internal schedule the Renesas is working on. 

• 
  Usual timing is 2-3 months after Yocto release for KF release from Cogent plus another 2-4 weeks for IoT.bzh to perform QA and prepare the update for AGL. 
• 
  They have separate project to update to kernel 5.4. Current plan for H3/KF is to switch to 5.0.  We requested that they look at a plan to switch to 5.4 ASAP for 3.1. 
• 
  We would like to know Renesas plans for supporting 3.1. Will they support for the two year term of the YP LTS?

 
Recommendation from SAT is to switch to  #
Populate the next branch with Yocto master/3.1 so that the BSPs can start their work in advance. 

1. Leave AGL/master on Zeus until 3.1 is released and Renesas BSP is ready. Assume that RPI, Intel, BBE will be ready on day 1 of 3.1 release.

2. 
   Move AGL/next to master once the Renesas BSP (4.14) for starter kit (probably not KF) is released and integrated into /next.  
3. 
   Some point later in the year Renesas will update to kernel 5.4 (hopefully ready Oct/Nov).
4. 
   To be considered.  AGL would stay with YP 3.1 for two years. Need to check with board vendors on their plans for YP support.