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
On Apr 27, 2012, at 6:29 PM, Dirk Pranke dpra...@chromium.org wrote:
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
On Sun, Apr 29, 2012 at 12:37 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 27, 2012, at 6:29 PM, Dirk Pranke dpra...@chromium.org wrote:
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
On Apr 29, 2012, at 1:04 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Sun, Apr 29, 2012 at 12:37 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 27, 2012, at 6:29 PM, Dirk Pranke dpra...@chromium.org wrote:
BTW, the page at https://trac.webkit.org/wiki/DeprecatingFeatures seems
to be
On Sun, Apr 29, 2012 at 1:08 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 29, 2012, at 1:04 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Sun, Apr 29, 2012 at 12:37 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 27, 2012, at 6:29 PM, Dirk Pranke dpra...@chromium.org wrote:
BTW,
On Apr 29, 2012, at 1:18 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Sun, Apr 29, 2012 at 1:08 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 29, 2012, at 1:04 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Sun, Apr 29, 2012 at 12:37 PM, Maciej Stachowiak m...@apple.com wrote:
On Apr 27,
Hi Julien,
Thanks for the writeup! I definitely wanted to be in that discussion
but it conflicted with another discussion I wanted to be in. It looks
like I more or less agree with the writeup, though :).
That said, what sort of officialness does this
writeup/guideline/policy have? Do all the
On Fri, Apr 27, 2012 at 2:18 PM, Dirk Pranke dpra...@chromium.org 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
Is the concern that we've been deprecating too many things too quickly?
On Fri, Apr 27, 2012 at 5:00 PM, Benjamin Poulain benja...@webkit.org wrote:
On Fri, Apr 27, 2012 at 2:18 PM, Dirk Pranke dpra...@chromium.org wrote:
That said, what sort of officialness does this
writeup/guideline/policy
On Fri, Apr 27, 2012 at 5:10 PM, Eric Seidel e...@webkit.org wrote:
Is the concern that we've been deprecating too many things too quickly?
Quite the contrary. People were concerned about the way to deprecate
more stuff and making fewer mistakes when adding and removing features
:)
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
Not having been to the meeting (but having read
https://trac.webkit.org/wiki/DeprecatingFeatures), it struck me as
though we were trying to add process (like we did for adding features
last year), to deter deprecating things.
On Fri, Apr 27, 2012 at 5:14 PM, Benjamin Poulain benja...@webkit.org
On Fri, Apr 27, 2012 at 5:17 PM, Maciej Stachowiak m...@apple.com wrote:
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
Hi WebKittens,
following the talk about Deprecating (web-facing) features and vendor
prefixing [1], we decided to create a guideline covering new
deprecations or un-prefixing [2]. The rationale is that this will
avoid a lot of the mistakes that we have made in the previous
deprecations and that
14 matches
Mail list logo
