- "What guarantees do we have that the extension won't break in the next browser security update?"
The extensions all use each browser's built-in extension mechanism, we don't rely on specific mechanisms besides that only the "public" browser extension api. We have (will) to keep track of the changes in this area to make sure that nothing breaks, (and update what's needed if it does), - "Are there tests (preferably automated) that can be run to verify that the new browser works with the old extension?" We have automated integration tests that are being run daily to make sure that basic integration happens. These are based on autopilot's desktop introspection caps, - "Who will be doing this testing?" See above, our QA team does take care of maintaining (and expanding) them, - "Who is maintaining the browser extension code in stable releases?" The WebApps team does, - "I have quite a few concerns here because these updates come every 3-6 weeks and we don't want to have to decide between providing a timely, important security update to our users and breaking the browser extension (and therefore webapps)." This is a very valid concern, and we are 100% aware of that. We tried to make sure that the QA infrastructure is ready for that, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043461 Title: [FFE] Update WebApps to support dpkg distribution mechanism To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1043461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
