Releases/Firefox 21/Test Plan: Difference between revisions

Jump to navigation Jump to search
 
Line 3,490: Line 3,490:
*** had they be testing Nightly 3 months ago we'd have known about it
*** had they be testing Nightly 3 months ago we'd have known about it
** Should look at having mozilla-central opt tinderbox builds for longer so we can regress further
** Should look at having mozilla-central opt tinderbox builds for longer so we can regress further
*** current pushlog is large, bug regressed 3 months ago, we could regress it further if we had builds
*** current pushlog is large, [http://playbingoonline.es/ Sun Bingo] bug regressed 3 months ago, we could regress it further if we had builds
*** rebuilding random changesets in that range is not too feasible
*** rebuilding random changesets in that range is not too feasible
* {{bug|842334}} Ensure distribution directory is still at the top level after the move of the browser into the browser directory
* {{bug|842334}} Ensure distribution directory is still at the top level after the move of the browser into the browser directory
Line 3,498: Line 3,498:
** Can/should we involve Tomcat/Hong in the sign-off process for future RCs? QA lacks the expertise and tests to be able to reasonably qualify custom distributions
** Can/should we involve Tomcat/Hong in the sign-off process for future RCs? QA lacks the expertise and tests to be able to reasonably qualify custom distributions
* {{bug|870834}} Shutdown crash @ PR_Free _pt_thread_death_internal
* {{bug|870834}} Shutdown crash @ PR_Free _pt_thread_death_internal
** Found by Bob Clary via crash automation, first occurred on April 30
** Found by Bob Clary via crash automation, [http://bestfreepokergames.co.uk/ Poker Games] first occurred on April 30
** Why did it take us 10 days to file a bug?
** Why did it take us 10 days to file a bug?
* {{bug|871851}} Firefox 21.0build3 updates on releasetest are broken, file size inconsistency
* {{bug|871851}} Firefox 21.0build3 updates on releasetest are broken, file size inconsistency
** caused by build3->build4 updates on test channel
** caused by build3->build4 updates on test channel
** does RelEng have automation to detect this?
** does RelEng have automation to detect this?

Navigation menu