666498 - Platform bug fixes in need of verification

Status: RESOLVED FIXED

(Mozilla QA Graveyard :: MozTrap, defect)

Description

[Carl Meyer (:carljm)]

Some platform bugs have been marked as fixed, and the fixes need verification (and for some, UI code changes to adapt). The following bugs currently need this:

https://bugzilla.mozilla.org/show_bug.cgi?id=665785
https://bugzilla.mozilla.org/show_bug.cgi?id=665135
https://bugzilla.mozilla.org/show_bug.cgi?id=665108
https://bugzilla.mozilla.org/show_bug.cgi?id=665102
https://bugzilla.mozilla.org/show_bug.cgi?id=656740
https://bugzilla.mozilla.org/show_bug.cgi?id=656697

I started on this, but was blocked by the regression https://bugzilla.mozilla.org/show_bug.cgi?id=666496 which prevented me from creating the necessary test data to check the others.

Comment 1

[Cameron Dawson [:camd]]

A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/14915343

Comment 2

[Cameron Dawson [:camd]]

Carl Meyer added a comment in Pivotal Tracker:   
   
Not sure how much priority to give this task, relative to working on .4 features. Checking platform fixes is time-consuming, and usually involves finding regressions. For now, going to leave everything running at the version of the platform prior to the latest round of changes.

Comment 3

[Cameron Dawson [:camd]]

Carl Meyer added a comment in Pivotal Tracker:   
   
FWIW, none of the above-listed platform fixes are for .4 features needing API.

Comment 4

[Cameron Dawson [:camd]]

Carl Meyer added a comment in Pivotal Tracker:   
   
also https://bugzilla.mozilla.org/show_bug.cgi?id=665116

Comment 5

[Cameron Dawson [:camd]]

Carl Meyer added a comment in Pivotal Tracker:   
   
666496 regression was fixed, took another stab at verifying these, blocked this time by another regression, https://bugzilla.mozilla.org/show_bug.cgi?id=666833

Comment 6

[Cameron Dawson [:camd]]

Carl Meyer added a comment in Pivotal Tracker:   
   
Cam, please let me know if any of these platform fixes seem to you like things that would be nice to get into the 0.3 staging deploy. Otherwise my plan is to only move to the newer platform version with the master (0.4 development) branch and leave 0.3 where it is. Otherwise I'm worried about the potential for platform regressions that my testing doesn't catch causing problems with the staging deploy that people are actually trying to use.

Comment 7

[Cameron Dawson [:camd]]

Carl Meyer changed story state to started in Pivotal Tracker

Comment 8

[Cameron Dawson [:camd]]

Carl Meyer added a comment in Pivotal Tracker:   
   
Ok, I've checked and either verified or reopened all of these.

Cam, I'm going back to marking platform bugs Verified when I test them out manually, because I do want a way to record when I'm satisfied that the feature works. I'd still like to have a sense that these bugs are all going to be reflected in platform test cases in your test suite at some point, so it'd be good if we had a way to mark that.

Comment 9

[Cameron Dawson [:camd]]

Carl Meyer changed story state to accepted in Pivotal Tracker