Bugs for S60 port
Hi there, As you may or may not be aware, a branch has been created for the S60 port of WebKit. Also, quite recently, a couple of new S60-related platforms were added to the WebKit product's platform list. We were wondering if it's OK with everyone to start migrating a bunch (say roughly 15/25) of errors related to the S60 port into Bugzilla? Some of these errors will have been fixed in the ToT (like [1]) but some may not be (like [2]). Of course, we're more than happy to assign the bugs to people working in the S60 branch! The plan is at this stage to create them against the WebKit product but differentiate them a little by having an S60-related platform value, but I'm not sure if that makes people's life hard. If so maybe I could talk to Joost or someone about potentially getting an S60WebKit product, but we'd rather stick with the WebKit product ... Many thanks, Bradley [1] http://bugzilla.opendarwin.org/show_bug.cgi?id=8959 [2] http://bugzilla.opendarwin.org/show_bug.cgi?id=8950
So what's the process you envision as far as fixing the bugs? If the bug is fixed on ToT, do you plan to backport the fix to the S60 branch? If it's broken in both the S60 and ToT branches, will the bug be fixed in both places? I'm just curious as to the direction that the S60 branch will be going in, e.g., will it eventually get merged with ToT, or will it be a parallel branch of development (pulling in fixes and changes from ToT as needed) in perpetuity? Dave On May 22, 2006, at 6:38 PM, <bradley.morrison@nokia.com> wrote:
Hi there,
As you may or may not be aware, a branch has been created for the S60 port of WebKit. Also, quite recently, a couple of new S60-related platforms were added to the WebKit product's platform list.
We were wondering if it's OK with everyone to start migrating a bunch (say roughly 15/25) of errors related to the S60 port into Bugzilla?
Some of these errors will have been fixed in the ToT (like [1]) but some may not be (like [2]).
Of course, we're more than happy to assign the bugs to people working in the S60 branch! The plan is at this stage to create them against the WebKit product but differentiate them a little by having an S60-related platform value, but I'm not sure if that makes people's life hard. If so maybe I could talk to Joost or someone about potentially getting an S60WebKit product, but we'd rather stick with the WebKit product ...
Many thanks, Bradley
[1] http://bugzilla.opendarwin.org/show_bug.cgi?id=8959 [2] http://bugzilla.opendarwin.org/show_bug.cgi?id=8950
So what's the process you envision as far as fixing the bugs?
Long term, we are aiming to not have our own major branch. Just small stabilization branch for different phone releases.
If the bug is fixed on ToT, do you plan to backport the fix to the S60 branch? If it's broken in both the S60 and ToT branches, will the bug be fixed in both places?
It should be fixed in ToT first, and backported to the S60 branch.
I'm just curious as to the direction that the S60 branch will be going in, e.g., will it eventually get merged with ToT, or will it be a parallel branch of development (pulling in fixes and changes from ToT as needed) in perpetuity?
Our aim is to merge with ToT. I believe we may still need branches as we stabilize versions to go out with phones. Development should happen on ToT. As you may be aware, Safari is currently on it's own branch too. I hope to see Safari move to ToT too in the future. DavidC
Dave
On May 22, 2006, at 6:38 PM, <bradley.morrison@nokia.com> wrote:
Hi there,
As you may or may not be aware, a branch has been created for the S60 port of WebKit. Also, quite recently, a couple of new S60-related platforms were added to the WebKit product's platform list.
We were wondering if it's OK with everyone to start migrating a bunch (say roughly 15/25) of errors related to the S60 port into Bugzilla?
Some of these errors will have been fixed in the ToT (like [1]) but some may not be (like [2]).
Of course, we're more than happy to assign the bugs to people working in the S60 branch! The plan is at this stage to create them against the WebKit product but differentiate them a little by having an S60-related platform value, but I'm not sure if that makes people's life hard. If so maybe I could talk to Joost or someone about potentially getting an S60WebKit product, but we'd rather stick with the WebKit product ...
Many thanks, Bradley
[1] http://bugzilla.opendarwin.org/show_bug.cgi?id=8959 [2] http://bugzilla.opendarwin.org/show_bug.cgi?id=8950
_______________________________________________ webkit-dev mailing list webkit-dev@opendarwin.org http://www.opendarwin.org/mailman/listinfo/webkit-dev
participants (3)
-
bradley.morrison＠nokia.com
-
David D. Kilzer
-
David.Carson＠nokia.com