Bugs are good for communicating discrete tasks, but I feel a monthly
check-in would be healthy for the project.
With that in mind, let this be the first volume of "What's up, Bugzilla?"
This will obviously not be exhaustive, and is just from my perspective. :-)
I'm getting pretty excited about the hopefully-soon release of 6.0.
Having the sandstone skin as default
the cleaner REST framework (which will hopefully allow us to have more
RESTy APIs in the future),
faster memcached (both Cache::Memcached::Fast and the recent patch
to remove (un-needed) detainting)
a standard-ish perl dependency situation, and a pretty friendly
out-of-the-box development experience, these are just some of my
favorite things. :)
Things To Do for the 6.0 release.
1) Currently :justdave is reviewing Bug 988971, but nothing stops
other people from taking that patch and applying it to master,
and reporting back their findings. Doing that would definitely be
2) I'm sure :dkl and/or :LpSolit wouldn't mind someone becoming
familiar with the release note process. There is a guide for it .
3) I've been trying to create higher-quality bugs, especially when I
can't find time to work on them. Many of these are performance
- Using Sereal for memcache would yield a good boost for sites
using memcached .
- Being smarter about creating custom fields in Bugzilla::Bug
object. One approach is described in the user story field .
- There's no bug open for this, but I would like to have more
tests for our Markdown implementation. This is probably the easiest to
test component of the whole system,
and we've had a lot of formatting bugs .
There are things to look for beyond 6.0: The Modal UI, used on BMO, is
probably not going to make the 6.0 release.
Development of it on the BMO side of things is progressing at a
furious rate and it is likely to be defaulted to on at the end of this
The task of making that work for vanilla Bugzilla is straight-forward
A good first step for this would be getting Needinfo included as a
It's not so much asking for help (we'll get to where we're going
eventually) but more to communicate what's going on, and to highlight
that someone else *could* do without having to invest a significant
amount of time.