Today I've worked on improving the nightly build support on CI, and nightly builds are now finally available as individual files instead of being zipped into one big one.
This means it's now easier for people on macOS and Windows to test the latest changes before they are released, by simply going to the latest nightly build and grabbing a macOS/Windows build under "Artifacts".
This now also includes builds of the qt6-v2 branch, and I'd really welcome having some more testers there! qutebrowser developers (and some brave[*] users) have been using it as daily driver since a while, and it's generally regarded to be ready to use. If you are on Linux, there's mkvenv.py support, Flatpak builds and an Archlinux AUR package available too, see the issue for all the details.
Please give it a spin and open a new issue if you run into any trouble!
There still is a lot of work to do to actually integrate this into the master branch and getting qutebrowser v3.0.0 out, but most of the remaining work is stuff behind the scenes now - from an user's perspective, the qt6-v2 branch should be pretty much ready.
For the next few weeks, my plan is to get back to merging some PRs, and regularily rebase the qt6-v2 branch on master to get them in there as well. I'll also start teaching Python at the university again in September (until February), so the clock is ticking a bit... I'm hoping that I'll still be able to work on qutebrowser and get this all wrapped up on the side though (only teaching two days a week, plus preparation/admin stuff).
[*] The English word, not the browser ;)
- CVE-2021-41146: Arbitrary command execution in qutebrowser on Windows via URL handler
- qutebrowser moving to Libera Chat
- Paying it forward
- Paving the road towards qutebrowser v2.0
- 2019 qutebrowser crowdfunding - reminder
- qutebrowser meetup Berlin (2019-11-28)
- 2019 qutebrowser crowdfunding with shirts, stickers and more!
- Current qutebrowser roadmap and next crowdfunding
- Crowdfunding 2019 ideas
- Happy birthday, qutebrowser!
- CVE-2018-10895: Remote code execution due to CSRF in qutebrowser
- qutebrowser v1.3.3 released (security update!)
- qutebrowser v1.2.0 released!
- T-Shirts shipped, initial implementation of per-domain settings
- Current state of per-domain settings
- qutebrowser v1.0.0 released!
- qutebrowser v1.0.0 is coming closer
- New config merged!
- Config revolution - Part 1 finished
- Refactoring more things, a working YAML config, and more!
- Refactoring all the things!
- First week
- First 2 days
- Getting started again
- Second qutebrowser crowdfunding launched!
- qutebrowser v0.10.0 released
- Wrapping up and looking at the future
- Days 39/40/41: Lots of features!
- Days 37/38: Hints in master, tests
- Day 36: Hints!
- Days 33-35: Mouse functionality, and rewriting hints
- Days 31/32: More web elements
- Days 29/30: Web elements
- Days 27/28: Settings and web inspector
- Day 24-26: Refactoring the WebElement API
- Day 21-23: After Europython and releases
- Day 19/20: Bugs everywhere!
- qutebrowser v0.8.0 released
- Day 17: Printing and searching
- Sending out qutebrowser and pytest stickers
- Day 15/16: Merged!
- Day 13/14: Almost merged!
- Day 12: Tests running!
- Day 10/11: Refactoring!
- Day 9: A bit of everything
- Day 8: More fixing and pytest sprint/training
- Day 7: Fixing things
- Day 6: Branching off
- qutebrowser v0.7.0 released
- Day 4: Playing whack-a-mole
- Day 3: Last pull requests and managing requirement files
- Day 2: More pull requests and nicer test output
- Day 1: Merging pull requests, and a stupid bug
- About and Timeline