Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This is a limited release with only three features and no other features and fixes to RDK6.0 will be accepted. Same platforms as 6.0 

Features

  1. Webkit 2.38.12 Epic RDKVREL-8. Support RDKDEV-432 (Documents some Sanity Tests to be used, some test reports and  some test issues)
  2. Thunder 4.2 Epic: RDKVREL-7  UserStory RDKDEV-643
  3. YT 2024.  EpicEpics: RDKVREL-91 & RDKVREL-208
  4. WebKit 2.38 will follow the Comcast Test Plan for browser: WPE Upgrade Test Scope plus the TDK Test 'Sanity' / 'Regression Suites' : as attached to TDK-7152 (RDK_Sanity_Suite, UI_SanityTestSuite and RDKV_BCM-SGM-sanityTest-Cases

...

  1. )

Thunder 4.2 will follow the TDK Sanity Test suites per excel spreadsheets: RDK_Sanity_Suite and UI_SanityTest_Suite  and   Regression Tests every feature. (Anand published mail chain?)

Acceptance Criteria not defined.  

YouTube 2024 Requires Google Certification


Overall Status

Platforms teams working on integrating Webkit 2.38 and Thunder 4.2 on a feature branch. Required changes are being cherrypicked from rdk-next to this feature branch. Changes will be merged to the feature branch once builds are working. The changes will be cherrypicked to rdk6-main once ready for testing. There will be 3 release candidates:

RC.1 Jan 8th - Target for Feature delivery

RC.2 Feb 5th 21st- Bug fixing

RC.3 March 4th 18th - Bug fixing

RDK6.1 March 29th - Release Need cross platform feature owners who can make decisions on requirements , acceptance testing etc.

BRCM / Sagemcom Status

Stiletto / BRCM7126  are not part of this release. This is being worked by Rajapriya for RDK7 - (needs new BRCM SDK and move from ACK5.1.0 to 5.1.1). No specific RDK6.1 sprint plans in December -aim is to have build issues resolved.  Power Management fixes on rdk_next not being targeted for RDK6.1

Webkit 2.38

  • TDK tests and CPE test utility to be run on feature branch next week (week of 25th Dec.) Env setup currently in progress for TDK resting - Elizabeth helping. RDKVREL-99
  • Kieran to be added to weekly status emails. 
  • Key issues: Cast/XDial not working, key mapping issue, Home key issue, YouTube signing persistence across reboot (all platforms - UI ticket)
  • .
  • Changes merged to rdk_next by Broadcom  - 2.38 now the default.  Web Audio not working,  issue now a blocker. BCM72180-821
  • CPE test utility (Browser Test Tool : B2T Tool)and browser test suites in scope. (Browser Tests - Shilpa) Akhil requesting detailed test procedures form Comcast. Acceptance criteria clarified.
  • BRCM and Sagemcom have been validated on rdk_next - some issues related to key mapping being worked. nex .  Test Report
  • Changes will eventually need to be cherry picked to rdk6_main.

Thunder 4.2

...

  • A very large number of changes to be reviewed and changes  brought to rdk6_main - will take time. RC.1 won't be Jan 8th 12th ready.
  • .
  • Feature being worked on feature branch
  • Changes be tracked in excel (here - Sooraj)
  • Team facing multiple build errors with BRCM Ref build (Philip + H Kumar). Working with Akhil's team on these. Sagemcom build not being tried yet. 

YT24 - RDKVREL-91

  • YT24 changes on rdk_next. Distro to be enabled. Verified encrypted and clear playback in local build.
  • DME Apps +SDK24 + ACK15.1.3 Jan 19th delivery. (Kirkstone by March (Q1) - so delayed start for RDK7..)
  • BRCM dev team task is to take delivery of the DME apps and do sanity test - no certification required as its already certified by Broadcom
  • Changes expected on stable2 in 2 weeks. (by 21st Dec) - changes to meta-rdk-video to enable the Distro.
  • Shibu's team doesn't have BRCM platform and unlikely to be testing on Sagemcom.

Rpi-4 Status


QAM fix on rdk-next will not be part of the release and will not be brought to rdk6-main. Work on rdk6.1 started 5th DecemberWebkit 2.38

...

Webkit 2.38

  • Feature branch build successful - starting tdk sanity testing on that. (later will run Browser tests - assuming PIF will do performance comparisons with 2.28)
  • 3 people running tests expect to complete TDK testing next week (week of 25th Dec) and also 50% of Browser tests.
  • Sanity testing progressing okay on rdk-next. 
  • Build issue on rdk-next related to QAM Rpi Hybrid profile - not a problem on rdk6_main which doesn't support QAM on RPi4 (rdk-next issue probably a config file change needed for cmake 3.5 on rdkservices - sync with Karuna/Simon on that fix)
  • New build error on rdk-next with respect to Alexa, being worked by Arun / Akhil. 

Thunder 4.2

  • Sanity test almost done on rdk-next but blocked by new build error related to QAM. 
  • Feature build  being worked Feature build completed on feature branch by Akhil / Rosna  

YT24

  • Not started - changes Changes are merged to rdk_next
  • YT23 stopped working - libcobalt no longer supported by Google - need to migrate migrated to evergreen.  Will do this migration prior to moving on to YT24.  2 people working on that

Other

  • RPI-4 IPSTB port completed - running fine. James to determine what is issue with his sanity tests failing. 
  • H264 trickmodes currently blocked as need to be worked by gstreamer expert. Chitan said he would support however better if he works on this full time. Delia ticket to be assigned to him and and request he takes it up for sprint.rmf deferred as rmf not to be supported in RDK7, AAMP will need to be addressed in RDK7 time frame. 

Amlogic / AmlogicTV / Skyworth Status

...

Thunder 4.2

  • Ran on rdk_next will need to and rerun on feature branch. Feature branch has some local changes (Aamp) need to integrate those and close out on everything to be brought to feature branch (Suresh call on Tuesday 12th)
  • Question gone to Bart on his expectations - however Bart is not driving the release content.
  •  
  • Web audio issue is only key issue so far. Have run sanity on sanity - not full sanity. Will run run full sanity on clean feature branch.Resolved

YT24

  • Certification in progress - Google reviewing tomorrow. Changes done on branch - once approved by Google will bring to rdk_next. Expect to do this by 15th Dec.completed - Google reviewed 

RealTek / Sercomm Status

Webkit 2.38

Thunder 4.2

  • Ran on rdk_next will need to rerun on feature branch. Feature branch has some local changes (Aamp) need to integrate those and close out on everything to be brought to feature branch (Suresh call on Tuesday 12th)Question gone to Bart on his expectations - however Bart is not driving the release content.
  • Web audio issue is only key issue so far. Have run sanity on sanity - not full sanity. Will run full sanity on clean feature branch.Resolved

YT24

  • Certification in progress completed - Google reviewing tomorrow. Changes done on branch - once approved by Google will bring to rdk_next. Expect to do this by 15th Dec.reviewed.