In addition to the Mojolicious ❤️, we’re also focused on more near-term gains.
Specifically getting the Bugzilla/Harmony branch running under PSGI, and being a thing you can download and use.
I am happy to announce today that the master branch is in a beta-quality state as of today,
At the moment, the following installation scenarios have been tested:
- checkout the code
cpanm --installdeps --notest --with-feature=bmo -l local .
checksetup.pl and edit localconfig to point your database (only mysql is currently working)
- run app.psgi, optionally with starman
If you would like to help the project, a good place to start would be testing this on your systems and reporting back findings.
The next milestone will be integration of the Mojolicious work currently going on in PR #517 in the bmo repo
Thanks to the near-heroic efforts of CyberShadow the unstable harmony branch is getting quite close to being able to run as an independent Bugzilla install.
For a number of reasons, bmo has a separate repo for managing its dependencies. Mostly this is about efficiency — dependencies change less often then the code, and we can have much faster builds and CI.
In a step towards independence I have forked the “bmo-systems” repo as harmony-systems, and with any luck the “unstable” branch of the harmony repo will soon be passing its own tests.
Note that the eventual goal is for the bmo and harmony repositories to be “nearly identical”, differing only in disabled extensions. That said, we need flexibility at times to experiment.
So after staring at a wall for a while, I realized it was lingering code in the ‘BMO’ extension causing my non-working-ness from Saturday.
So current status is that a checkout of bugzilla/harmony‘s unstable branch should be runnable now.
cpanm --with-feature=bmo --installdeps .
then edit localconfig to point db_host to a mysql db, set urlbase to http://localhost:5000/, and then
Of course, running checksetup a second third is currently broken, but I suspect another round of poking at things and that will work.
- re-enable SecureMail (and merge its schema into core
- disable BMO extension in harmony (and test stuff)
- make tracking flags optional (maybe; maybe we want it in the core)
- split out schema migration from checksetup
PSGI seems pretty stable, so now to make the rest actually work!
First I’m moving schema changes out of extensions. This doesn’t pass tests yet — and it is not complete. I’ll have to update templates as well.
Next, a lot of our UX code assumes a workflow that is different than the default values. Ideally we’d support changing the workflow, but for the moment
the default workflow provided should be the one the bmo one.
Finally, we’re still getting an error because the product security group doesn’t yet have a good default. My early attempt this is not entirely working…
From now, whatever the last thing I’ve been working on will be in this unstable branch, because in a week or two I hope to have master in a consistent, release-ready state.
I’ll spend a bit of time Sunday as well, and hope to have something runnable without having to run the