OTA release Process Flow
2017-09-07 19:46:03 10 举报Process for OTA RELEASE.
作者其他创作
大纲/内容
Provide validate result to PI PM(Project PI Tech)
Upload BOTA to CDSP & Deploy BOTA package(DPM)
Factory Release after RRR
Technical Approvals(PI PM) (1)
Issue review make decision(Core Team)(3)
Estimate SWRP items(SME)(6)
Validate CFC package(PI Tech)
Full SQA approval in JIRA(PI PM) (4)
Launch Call CR Approval(Leaders)(8)
Technical Approvals(PI PM)
Release notes URL(Service Team)
Plan for new SW version production(Factory) (1)
Same with OTA release.
OTA Release after RRR
Trigger HW estimate SAR assessment and collect result.(PI PM) (7)
Full Deploying Release(DPM) (5)
Approve to start Soak(TAM)
Check the SW version(Requestor)
Formal Notification(PI-Minghua)
2~10 days
3~5 days
Provide Soak result(Call Center)
Notify SW Dev team(SPM)
End
NO
Raise issue(Requestor)(1)
2 days
Get Google TA(PI PM)
3 days
Yes
PI Tech notice Service Team to start URL production.
Provide SW version(SPM)
Write Release note & BOTA text(PI Tech) (9)
Usually 2 days ~ 1 months
Provide check result(Requestor)
Soak Test(DPM)(3)
RRR
Application for Google TA(PI PM)(4)
Before RRR
Submit a DPM CR(PI UT)
Release note & BOTA text translation(Localization Team)
1-2 days
If resolve issue
Build CFC package(PI Tech)
Soak Result Review(DPM/PI PM)
Pre-soak(PI UT)(2)
Create BOTA package(PI CM)
职业：暂无
0 条评论
下一页
