This is a list of known release blockers for Bugzilla Harmony, in prority list order.
We can and should only support current and previous releases of MySQL. People coming from MySQL 5.6 or earlier should be nudged to use utf8mb4, which allows for emojis and some obscure languages.
Currently harmony will work with MariaDB 10+ (any version), but will not function in MySQL 8 due to the word "groups" becoming a reserved word.
Checksetup needs to be updated help the user understand if their mysql can work.
For MySQL 8, either:
- We commit to supporting mysql 8
- We detect mysql 8 and direct the user to use either mysql 5.7 or mariadb
The later option is not very pleasant. I believe the code I wrote over a year ago could allow us to support mysql 8, and that's in this branch
I think most of the postgres incompatibility is in the "BMO" extension, and in order to be able to release I now believe we should remove the BMO extension from our codebase. This is unfortunate because it has a lot of useful features, but given resource constraints it is the best move.
Bugzilla::Logging controls how the application logs. It has support for defaults, but those defautls were written for BMO and don't make sense for the app.
This is left a bit vague, but here's the guiding principal: when you install bugzilla it needs to log in a place you expect it to.
I would like the Dockerfile to be rewritten such that the ENTRYPOINT is the bugzilla.pl script, so that the container can be used as a drop in replacement for the bugzilla.pl executable.
It would be good to add sub-commands for checksetup and the jobqueue to this. bugzilla.pl sub-commands can be defined in the Bugzilla::App::Cmd::* namespace.
If we release harmony and it has a good (amd small!) container, it will look good.