Bugzilla 6 Backend Roadmap

What can we do before the release of Bugzilla 6.0 in (August) 2018?

PSGI Support

• Re-create the PSGI support that was added by LpSolit to the bugzilla master branch.
• Provides an (so far undocumented) Bugzilla::Extension hook for adding to the plack builder env. This is used by the bzapi extension for instance.
• init_page() is called within a CGI context.
• CGI::Compile is loaded early to prevent spontaneous exits
• explicitly prohibit running as a CGI
• Have Bugzilla::CGI actually be a Plack::Request object in disguise?
• Merge into BMO (ensure it does not cause regressions for mod_perl consumers)
• Verify (somehow) that all paths handled by apache are handled by PSGI

Supporting UX

• Support Markdown comments (using CommonMark, or CommonMarkGFM (dylan's github flavored fork)
• New APIs -- possibly using Mojolicious makes this easier for UX work?

Performance

• Preload all templates into memory
• (mod_perl only) don't stat .htaccess files
• Replace Bugzilla::Object id() and name() accessors with Class::XSAccessor
• Use HTML::Escape
• use Sereal for the database schema

Installation

• It should be possible to install and update bugzilla without checksetup.pl
• Easy to install for ubuntu, fedora, and archlinux users
• (under consideration) Fat-packable release artifact? w/o XS dependencies?

Upgrading from previous versions should be tested

• Upgrading from 4.2
• Upgrading from 4.4
• Upgrading from 5.0
• Upgrading from 5.1