We are planning to release Istio 1.2 in the next ~2 weeks and we need your help testing it to ensure the release is solid and meets your standards. While our automated unit tests, integration tests, e2e tests, performance tests, and long-running burn-in tests give us a pretty clear signal, we still need help from everyone in the community to step through our documentation and confirm our documentation actually works for Istio 1.2.
If you can help us, please:
Add your github handle to the testing signup sheet and put “X” against line items that you would like to test. If you cannot access this sheet, email linsun@us.ibm.com and I’ll share it with you.
Perform the test and if there are no bugs, replace “X” with “Done”.
If you run into bugs/issues then please open an entry in GitHub and add the link inplace of “X”.
There will be a Testing session on Wed 6/5/19 10am-12:30pm PT (You can find details off Istio Community Calendar).
This session is intended for people who have claimed items in the testing signup sheet to run tests, ask questions, get help, and raise issues.
Representatives from each component will be in attendance so please take advantage of it.
Also, I have tried to give access to folks who requested access to the testing signup sheet. If you need access, the best way is to request access to our Istio team drive as it gives you access to not only this testing signup sheet but all other docs. The instruction is posted https://github.com/istio/community/blob/f5260a05ccf63b4c47dee19cd5663ebc0ab9f2a1/WORKING-GROUPS.md, and copied below for your convenience:
The working groups generate design docs which are kept in a Team Drive. Anybody can access the team drive for reading and commenting. To get access simply join the istio-team-drive-access@ group. Once you’ve done that, head to Team Drive and behold all the docs.