Bug 39121 - [Qt] Tracker bug for release critical bugs for QtWebKit 2.1 release
Summary: [Qt] Tracker bug for release critical bugs for QtWebKit 2.1 release
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P1 Normal
Assignee: Ademar Reis
URL:
Keywords: Qt, QtTriaged
Depends on:
Blocks:
 
Reported: 2010-05-14 08:58 PDT by Simon Hausmann
Modified: 2011-05-09 07:52 PDT (History)
16 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Hausmann 2010-05-14 08:58:11 PDT 
This master bug tracks all the bugs that prevent us from releasing QtWebKit 2.1
Comment 1 Ademar Reis 2010-09-06 10:35:02 PDT 
No need to block Bug #44677 anymore since the cherry-pick script handles multiple master bugs.
Comment 2 Chang Shu 2010-10-15 10:21:49 PDT 
Add a P1 bug to 2.1 release.
Comment 3 Antonio Gomes 2010-11-04 22:17:19 PDT 
Since bug 44089 is blocking 2.1, bug 48450 that blocks it should be blocking 2.1 too.
Comment 4 Ademar Reis 2010-11-05 07:26:51 PDT 
(In reply to comment #3)
> Since bug 44089 is blocking 2.1, bug 48450 that blocks it should be blocking 2.1 too.

Not really.

I prefer to have a clear dependency tree instead of a flat list of dependencies, so I'm removing it. For example, if for whatever reason we decide that bug 44089 is not important anymore, so will be bug 48450.

The correct way to query for blockers is to use the dependency tree link. Don't worry, I won't miss a bug because of that. :-)
Comment 5 Kenneth Rohde Christiansen 2011-01-11 14:16:32 PST 
Time to close this one?
Comment 6 Ademar Reis 2011-01-11 14:35:53 PST 
(In reply to comment #5)
> Time to close this one?

Not until 2.1 is officially released.
Comment 7 Caio Marcelo de Oliveira Filho 2011-03-23 08:28:37 PDT 
Adding bug 46248 per Ossy request.
Comment 8 Ademar Reis 2011-04-18 11:27:12 PDT 
Closing bug: 2.1.0 has been tagged and a release announcement is going to be made today.

Any new issues should be reported on bug 50925 (the next update for the 2.1 main version).