Sure. I'll enable the testsuite in the build for now. Eventually when we have a more comprehensive test suite, I'll package the tests so that they can run as autopkgtest's instead.
At the moment, we have a single branch for Oxide (trunk), which is based on the Chromium dev channel. Eventually, we will have 3 branches (stable, beta and trunk), with beta and stable tracking the corresponding Chromium branches. Stable will be what is shipped in the distro, and there will be PPA's for the other builds (like we have for Firefox). We haven't created those yet because we're still adding the required bits for webapps. The plan for transitioning to a stable branch in the archive is: - Once we're happy to freeze the code (ie, we've got all of the major bits for webapps in), we will create a beta branch when Google next update their beta from the dev channel. - At this point, the code is frozen (other than bug fixes). - When Google then update their stable from beta (around 6 weeks later), we will create a stable branch from our beta. - From this point the archive will always contain the stable branch, although we might switch to beta or trunk early in a development cycle As for the supported architectures - we're mainly limited to the architectures that V8 has an assembler for, which is currently x86, x86-64 and arm (the same as Chromium). I believe that Google is working on aarch64 support. There are no plans to support other architectures, and anybody who wanted to add support for them would need to convince Google to include that support in V8 upstream (along with any other build system support for those architectures). We'd be unlikely to accept Chromium patches to add architecture support in V8 due to the burden that these would place on development (the patches would be huge, V8 is fast moving and we're probably going to be handling 1-2 Chromium dev updates per week) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293681 Title: [MIR] oxide To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1293681/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
