happy bmo push day!

the following changes have been pushed to bugzilla.mozilla.org:

  • [785219] Secure bugmail no longer includes subject of bug
  • [785800] release tracking flag refresh (18)
  • [786167] various “Use of uninitialized value” warnings
  • [785308] diagnostic logging for HTML emails sometimes giving empty emails
  • [785309] Profanivore is throwing “ascii “\xB4″ does not map to Unicode” errors
  • [726353] Add a default requestee to flags (schema changes only, implementation code to land soon)
  • [785917] Custom field descriptions are not properly escaped when displayed as bug list column headers

please note due to bug 785308 html bugmail is currently disabled.  this push includes additional logging to help us track why it’s failing.

edit: html bugmail has been re-enabled.

happy bmo push day!

the following changes have been pushed to bugzilla.mozilla.org:

  • [bug 783300] Create New Product For Mozilla.org Website called “www.mozilla.org” & Move Existing Bugs
  • [bug 781514] Better fix for “when loading a bug with IE all <select> fields are selecting the first item”
  • [bug 775275] Port HTML email support from Bugzilla 4.2 to BMO 4.0

html bugmail comes to bugzilla.mozilla.org

due to unforeseen delays in upgrading bmo to bugzilla version 4.2, we’ve back-ported and deployed html bugmail!

during our evaluation of bugzilla 4.2 it became clear that a feature of searching in 4.0 was not implemented when the searching backend was rewritten for 4.2. (bug 677757)

bmo isn’t running a standard version of bugzilla 4.0 — we have a large number of bugzilla extensions installed to provide a host of extended functionality, and we’ve also backported a lot of features and fixes from 4.2 and 4.4. when it became clear the issue with searching would delay the upgrade, we discussed at length which features in 4.2 we’re missing and the viability of backporting the features to 4.0. by and far the feature which garnered the most positive comments and feedback was html bugmail, and the decision was made to backport.

while i’ve been working on search, dkl took on the task of the backport (bug 775275), and we’ll be making those changes live today.

the initial default format for bugmail will continue to be text-only, use preferences to change to your preferred email format to html for a sneak peek.

we will change the default format for all users from text to html in approx 3 weeks.

if you run a system which parses bmo’s bugmail you may see minor differences in the text mail. if your system doesn’t support multi-part or html content you should login to bmo and change your account’s preference from ‘site default’ to ‘text only’.

edit: we’ve temporarily disabled html email while we investigate an intermittent problem with blank bugmail (bug 785308)

happy bmo push day!

the following changes have been pushed to bugzilla.mozilla.org:

  • [560465] provide an easy way for researchers to learn about how to get access to a limited copy of bugzilla.mozilla.org
  • [782330] Whine emails show the summary of security sensitive bugs
  • [783317] Fix interdiff breakage

note we’re still seeing some interdiff issues with some patches, unfortunately it isn’t a straight forward problem to resolve.

happy bmo push day!

the following changes have been pushed to bugzilla.mozilla.org:

  • [779434] refreshing a page does not update fields
  • [779862] shift patchreader to a bugzilla namespace module and fix long standing issues
  • [778971] A watched component doesn’t show up in my Component Watching preferences pane
  • [778631] use a persistent Template::Provider to avoid recompiling templates between page loads on mod_perl
  • [780849] incorrect auto-linkification of full CVE urls in comments
  • [765842] creation of a Finance product and custom bug entry form

two of these changes address long standing issues with bugzilla.mozilla.org:

diff/interdiff issues

bugzilla uses the cpan module PatchReader to parse diffs, which is used when viewing diffs and interdiffs. the current release of patchreader chokes on hg diffs due to the inline comments.

we’ve taken the step of bringing the code from patchreader into bmo’s codebase in order to patch this and a few other issues, as well as providing any/all patches to the upstream patchreader.

accidentally reverting someone else’s changes

a long standing problem is how bugzilla and firefox interact when a page has been refreshed between edits, has been addressed.

the problematic scenario is:

  1. you load a bug, and the priority is set to P3.  you change something else but don’t alter the priority field
  2. someone else edits the bug, and changes the priority to P1
  3. you refresh the page in firefox

before this week’s changes, after the page is refreshed firefox will remember that P3 was the selected priority, and that will stay selected. when you submit your changes you won’t encounter a mid-air collision warning because bugzilla can’t determine if the priority field was changed before or after your refresh, resulting in the priority “silently” being changed from P1 to P3.  this issue applies to all <select> fields, not just priority.

bugzilla now works around this issue by keeping a track of fields which you explicitly change, and after you refresh the page, any field which you didn’t explicitly change will be updated to the new value from the server.

[a-team] conversations with face

face is an irc bot i run on the #ateam channel.
its responses are purely random, drawing from past conversations on channel.

14:32 davehunt has left IRC (Connection reset by peer)
14:32 * face whistles and glances at the ceiling.
14:33 davehunt_ has joined the channel.

happy bmo push day!

the following changes have been pushed to bugzilla.mozilla.org:

  • [776897] Highlight trailing whitespace on lines in Splinter
  • [757698] update moco-ldap-check to run on a bmo admin server and generate a report for desktop support
  • [779472] Changes in swag request form
  • [779475] Changes in budget request form