Closed lexicalninja closed 3 weeks ago
@dumathane @TKDickson is this ticket still valid or can it be closed?
I don't believe Tom has documentation for this yet, so I imagine still relevant, but let's check with him - @DJUltraTom
@DJUltraTom is this still relevant? Therese mentioned above to check with you.
@TKDickson @DJUltraTom is this still relevant? If so what team should this fall under? ours?
i mean, technically its relevant to the new major versions from THIS year 😉
@bischoffa yes still relevant and it's home team work. Will add to the general QA home team epic. (I also put it on the epic that I created for the OS version sprint 0, a bit back)
@DJUltraTom any updates on this ticket?
https://docs.google.com/document/d/12edey_A85yTlOfEVRo1UAY2Lims9NSH2ewjIHBpR4Ec/edit Started a file to address questions and a proposal, will continue on this monday
above linked document has been updated. emails sent to QART team for feedback
@DJUltraTom given this is continuing into this sprint can you update the sprints to include the current one its in?
created 9182 for the next step of this process closing this ticket as both outcomes of this ticket have been met.
Task
Each year in the fall, both iOS and Android release new versions.
In order to maintain compatibility, the teams will need to test against release candidates of the new versions and raise any issues to be fixed prior to the new OS rolling out.
In order to accomplish this and to maintain a baseline for how we test these in the future, we will need to create the process for how the team with test, review and mitigate for new OS versions.
The output of this ticket should be the first draft of a testing plan, as well as an outline of a documentation page on how to load OS RC's and plan overview.
Questions
Outcomes