Description of problem: We do not make a note of what browser Beaker officially supports Version-Release number of selected component (if applicable): 0.12 How reproducible: Always Steps to Reproduce: 1. Try to find out what browser Beaker supports 2. 3. Actual results: Can't find it Expected results: Should be able to Additional info: We don't expect to find many oddities with how the Beaker UI looks/works between different browsers, but they are probably out there. We should publicly define what browsers we support (or at least what we test on, and thus what we expect should work), so people having a problem can be sure its a genuine bug, and not an oddity of their particular browser.
Since 0.15 starts making additional demands on the browser's JS and CSS support, we should get this documented for the final release.
On Gerrit: http://gerrit.beaker-project.org/#/c/2300/ Also notes the supported platforms for the command line client
Updated docs available at: http://beaker-project.org/docs-release-0.15/user-guide/interface.html http://beaker-project.org/docs-release-0.15/user-guide/bkr-client.html
verified on beaker-devel Version 0.15.0rc2(20130927)-->pass Steps: 1. visit: http://beaker-project.org/docs-release-0.15/user-guide/interface.html http://beaker-project.org/docs-release-0.15/user-guide/bkr-client.html 2. check the docs that notes what browsers Beaker supports and the supported platforms for the command line client Actual results: same as expected results. Expected results: should notes what browsers Beaker supports and the supported platforms for the command line client
Beaker 0.15 has been released.