WARNING: This server is unstable and will be retired in the next days.
If you want to keep this forum available, please request immediately a migration
on the Nabble Support forum.
Forums that don't receive any migration request will be deleted forever.
I think the concern is that, due to lack of clear standards, we end up not knowing when we can remove things. Thus, we end up with a lot of inconclusive and frustrating conversations, and people may shy away from even trying to remove things.
BTW, the page at <https://trac.webkit.org/wiki/DeprecatingFeatures> seems to be using "deprecate" in the sense of "remove entirely". Is that what is meant? If so, I think it would be helpful to change the wording to "removing features". In non-Web contexts, deprecate often means a step short of removal.
On Apr 27, 2012, at 5:10 PM, Eric Seidel <eric@...> wrote:
> Is the concern that we've been deprecating too many things too quickly?
> On Fri, Apr 27, 2012 at 5:00 PM, Benjamin Poulain <benjamin@...> wrote:
>> On Fri, Apr 27, 2012 at 2:18 PM, Dirk Pranke <dpranke@...> wrote:
>>> That said, what sort of "officialness" does this
>>> writeup/guideline/policy have? Do all the ports agree that this is
>>> what our stance should be?
>> Everyone seemed to agree we just need to discuss each deprecation on
>> webkit-dev with solid supporting data.
>> Feel free to continue the discussion on this mailing list if you have
>> ideas for improvement.
>> webkit-dev mailing list
>> webkit-dev@... >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > _______________________________________________
> webkit-dev mailing list
> webkit-dev@... > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev