Category Archives: mozilla

happy bmo push day!

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

  • [966042] Use of uninitialized value in string eq at Bugzilla/Extension/BMO/lib/Reports/UserActivity.pm line 42
  • [587701] Make it possible to hide “TinderboxPushlog Robot” spam
  • [961943] Nagios bug queue check support for paging regardless of severity
  • [968482] Bugzilla native REST API should default to application/json if no Accept header was set
  • [967607] User.get shouldn’t load data that requires extra database queries unless required

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [964299] bzr checkin regexp is a little too tight
  • [76498] QuickSearch: support comparison operators other than substring
  • [893641] change the maxlength of the component field in search results
  • [964856] Add a crash-signature field to Android Background Services
  • [957340] Make updates to the Gear Request Bug Form
  • [105865] bugzilla should pay attention to linebreaks when making bugnumbers to links

the changes to quicksearch are worth highlighting:
the default operator, colon (:), has always performed a substring match of the value. the following operators are now also supported:

  • : (substring)
    summary:food
    search for bugs where the summary contains foo
  • = (equals):
    summary=foo
    search for bugs where the summary is exactly foo
  • != (not-equals):
    summary!=foo
    search for bugs where the summary is not foo
  • > (greater-than):
    creation_ts>-2w
    search for bugs where that were created between two weeks ago and now, excluding bugs exactly two weeks old
  • >= (greater-than-equals):
    creation_ts>=-2w
    search for bugs where that were created between two weeks ago and now, including bugs exactly two weeks old
  • < (less-than):
    creation_ts<-2w
    search for bugs where that were created more than two weeks ago, excluding bugs exactly two weeks old
  • <= (less-than-equals):
    creation_ts<=-2w
    search for bugs where that were created more than two weeks ago, including bugs exactly two weeks old

discuss these changes on mozilla.tools.bmo.

renaming mozilla-corporation-confidential to mozilla-employee-confidential

in the early days of bugzilla.mozilla.org there were three bugzilla security groups which covered all mozilla employees: mozilla-corporation-confidential (mozilla corporation employees), mozilla-foundation-confidential (mozilla foundation employees), and mozilla-confidential (both corporation and foundation). as is the way, things change. the mozilla-confidential group got deprecated and eventually disabled. mozilla-corporation-confidential’s usage within bugzilla has expanded and is now the default security group for a large number of products. mozilla itself has made efforts to remove the distinction between the foundation and the corporation.

this has resulted in bugs which should be visible to all employees but were not (see bug 941671).

late on wednesday the 19th of feburary we will be renaming the mozilla-corporation-confidential group to mozilla-employee-confidential, and will update the group’s membership to include mozilla foundation staff.

  • if you are a bugzilla user (mozilla staff or otherwise), no action is required.
  • if you maintain a system which interfaces with bugzilla, an update may be required to adapt to the new name.

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [942599] Documentation about possible_duplicates() lists ‘products’ as argument instead of ‘product’
  • [748095] Bugzilla crashes when the shutdownhtml parameter is set and using a non-cookie based authentication method
  • [918384] backport upstream bug 756048 to bmo/4.2 to allow setting bug/attachment flags using the webservices
  • [956135] backport upstream bug 952284 to bmo/4.2 to hide tags set to private comments in the bug activity table
  • [956052] backport upstream bug 945535 to bmo/4.2 for performance improvement in bugs with large number of attachments

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [897810] Please add flag machine-state to the Release Engineering: Buildduty component
  • [908427] Once tracking flags are migrated, remove any unnecessary code in Bugzilla::Extension::BMO::Data used in the old tracking flags
  • [951020] Nagios bug queue checks should also support paging for a specific component
  • [815026] Bugzilla::Object cache should be cleared when an object is updated or removed from the database
  • [928989] add a new method to ember which just returns current values
  • [951442] Stop including attachments and comments in Ember.show API response
  • [950743] Navigating to Component Watching responds with a 500 on retrieving userprefs.cgi
  • [951016] X-Bugzilla-Mentors missing from email

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [947675] Bug id are sorted in wrong order on the dashboard
  • [885148] Commenting via patch details does not clear needinfo flag
  • [946353] Attachments should include can_edit field
  • [948991] Congratulations on having your first patch approved mail should mention which patch it refers to
  • [948961] Add “My Activity” link to account drop down in Mozilla skin
  • [928293] Add number of current reviews in queue on user profile
  • [949291] add link to a wiki page describing comment tagging
  • [946457] Add Ember.attachments API that includes possible flag values
  • [947012] The BIDW teams needs a new “product” on BMO

discuss these changes on mozilla.tools.bmo.

comment tagging deployed to bmo

i’ve been working on a bugzilla enhancement which allows you to tag individual comments with arbitrary strings, which was deployed today.

comment tagging features:

automatic collapsing of comments

the bugzilla administrator can configure a list of comment tags which will result in those comments being collapsed by default when a bug is loaded.

this allows obsolete or irrelevant comments to be hidden from the information stream.

comment grouping/threading

bugzilla shows a list of all comment tags in use on the bug, and clicking on a tag will expand those comments while collapsing all others.

this allows for simple threading of comments without diverging significantly from the current bugzilla user interface, api, and schema. you’ll be able to tag all comments relating to the same topic, and remove comments no longer relevant to that thread by removing the tag.

highlighting importing comments

on bugs with a lot of information, it can be time consuming for people not directly involved in the bug to find the relevant comments.  applying comment tags to the right comments assists this, and may negate the need for information to be gathered outside of bugzilla.

for example:

    • tagging a comment with “STR” (steps to reproduce) will help the qa team quickly find the information they need to verify the fix
    • writing a comment summarising a new feature and tagging it with “docs” will help the generation of documentation for mdn or similar

implementation notes

  • the “add tag” input field has an auto-complete drop-down, drawing from existing tags weighted by usage count
  • by default editbugs membership is required to add tags to comments
  • comment tags are not displayed unless you are logged in to bugzilla
  • tags are added and removed via xhr, changes are immediately visible to the changer without refreshing the page
  • tagging comments will not trigger bugmail, nor alter a bug’s last-modified date
  • tags added by other users (or on other tabs) will generally not be visible without a page refresh

happy bmo push day!

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

  • [941104] Default secure group for Mozilla Communities should not be “core-security”
  • [843457] PROJECT environment variable is not honored when mod_perl is enabled
  • [938161] sql_date_format() method for SQLite has an incorrect default format
  • [928057] When custom fields are added, a DBA bug should be created to update metrics permissions
  • [945501] create “Firefox :: Developer Tools: User Stories” component and enable the User Story extension on this component
  • [853509] Bugzilla version not displayed on the index page
  • [929321] create a script to delete all bugs from the database, and generate two dumps (with and without bugs)
  • [781672] checksetup.pl fails to check the version of the latest Apache2::SizeLimit release (it throws “Invalid version format (non-numeric data)”)
  • [938300] vers_cmp() incorrectly compares module versions
  • [922226] redirect when attachments contain reviewboard URLs
  • [943636] SQL error in quicksearch API when providing just a bug ID
  • [945799] I cannot change a review from me to someone else
  • [937020] consider hosting mozilla skin fonts on bmo
  • [942029] review suggestions only shows the first mentor
  • [869989] Add X-Bugzilla-Mentors field to bugmail headers and an indication to mentors in bugmail body
  • [942725] add the ability to tag comments with arbitrary tags
  • [905384] Project Kickoff Form: Change Drop Down Options for When do the items need to be ordered by? and Currency Request for Total Cost in Finance Questions

more information about comment tagging can be found in this blog post.

discuss these changes on mozilla.tools.bmo.

happy bmo push day!

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

  • [938763] Ember.show no longer works since the bug_check_can_change_field hook added to TrackingFlags ext
  • [939093] Unclosed <a> or misplaced code in “QA Contact: (edit) (take)”
  • [932034] Ember.show API doesn’t return can_edit property for dupe_of, blocks, and depends on fields
  • [939289] Ember.show API isn’t returning field or attachment changes properly when last_updated field is provided
  • [939717] do not normalise email addresses for gravatar
  • [937180] creation_ts of bugs and attachments always at 0 seconds in API calls
  • [936241] Bug.create doesn’t allow tracking flags to be set, but Bug.update does
  • [939844] seconds are no longer shown on a comment’s time
  • [935570] create an anti-spam extension
  • [929345] bug history/activity shouldn’t collapse multi-line values to a single line

discuss these changes on mozilla.tools.bmo.

improving bug update times

at the end of october we landed bug 910565 on bmo, which altered how bugmail is generated.

prior to that change, generating each recipient’s email blocked the completion of the update until all emails were generated and queued for delivery. with an average of 40 emails being sent for each bug change, the time we spent waiting on email generation could be significant.  the improvements are much more noticeable when marking a bug as a duplicate or adjusting intra-bug dependencies, where it wasn’t unusual for more than 100 emails to be sent.

the fix involves serialising bugzilla objects and pushing that into our worker queue.  bugzilla’s worker daemon now handles both email generation and delivery.

the following before/after graphs of the time taken to update bugs clearly demonstrate the improvements:

create/update response times - october

create/update response times – october

create/update response times - november

create/update response times – november

 

 

Follow

Get every new post delivered to your Inbox.

Join 75 other followers