Re: [webkit-dev] Best way to track feature evolution from release-to-release

2011-01-07 Thread Ojan Vafai
On Thu, Jan 6, 2011 at 8:57 PM, Ryosuke Niwa ryosuke.n...@gmail.com wrote: On Thu, Jan 6, 2011 at 8:31 PM, Darin Fisher da...@chromium.org wrote: Using svn revision numbers has the downside of not reflecting branches very well. A bigger number may correspond to a recent change to an old

Re: [webkit-dev] Best way to track feature evolution from release-to-release

2011-01-07 Thread Darin Fisher
On Fri, Jan 7, 2011 at 9:12 AM, Ojan Vafai o...@chromium.org wrote: On Thu, Jan 6, 2011 at 8:57 PM, Ryosuke Niwa ryosuke.n...@gmail.comwrote: On Thu, Jan 6, 2011 at 8:31 PM, Darin Fisher da...@chromium.org wrote: Using svn revision numbers has the downside of not reflecting branches very

Re: [webkit-dev] Best way to track feature evolution from release-to-release

2011-01-07 Thread Ojan Vafai
On Fri, Jan 7, 2011 at 9:24 AM, Darin Fisher da...@chromium.org wrote: On Fri, Jan 7, 2011 at 9:12 AM, Ojan Vafai o...@chromium.org wrote: Right. Having a shared version number across WebKit builds will never catch every case (e.g. patches pulled into branches, disabled features, etc.), but

Re: [webkit-dev] Best way to track feature evolution from release-to-release

2011-01-07 Thread Darin Fisher
On Fri, Jan 7, 2011 at 9:30 AM, Ojan Vafai o...@chromium.org wrote: On Fri, Jan 7, 2011 at 9:24 AM, Darin Fisher da...@chromium.org wrote: On Fri, Jan 7, 2011 at 9:12 AM, Ojan Vafai o...@chromium.org wrote: Right. Having a shared version number across WebKit builds will never catch every

Re: [webkit-dev] Best way to track feature evolution from release-to-release

2011-01-06 Thread Ojan Vafai
On Wed, Jan 5, 2011 at 9:38 AM, Darin Adler da...@apple.com wrote: The user agent string in Chromium cites, for example, AppleWebKit/534.10. Does this refer directly to the /tags/Safari-534.10 code base? In other words, this is just an example of an organization chosing to use a tag created

Re: [webkit-dev] Best way to track feature evolution from release-to-release

2011-01-06 Thread Darin Fisher
On Thu, Jan 6, 2011 at 4:39 PM, Ojan Vafai o...@chromium.org wrote: On Wed, Jan 5, 2011 at 9:38 AM, Darin Adler da...@apple.com wrote: The user agent string in Chromium cites, for example, AppleWebKit/534.10. Does this refer directly to the /tags/Safari-534.10 code base? In other words,

Re: [webkit-dev] Best way to track feature evolution from release-to-release

2011-01-05 Thread Tom Bahnck
Thank you. If my understanding is correct wrt to Apple's release process, when given the chance, Apple tags the WebKit trunk under the name Safari-### in the /tags directory. This contains all source from the WebKit trunk, including tools/bugzilla/test/etc. code. When making a Safari release,

Re: [webkit-dev] Best way to track feature evolution from release-to-release

2011-01-05 Thread Darin Adler
On Jan 5, 2011, at 7:06 AM, Tom Bahnck wrote: If my understanding is correct wrt to Apple's release process, when given the chance, Apple tags the WebKit trunk under the name Safari-### in the /tags directory. This contains all source from the WebKit trunk, including

[webkit-dev] Best way to track feature evolution from release-to-release

2011-01-04 Thread Tom Bahnck
I work on set-top box and PC-based media player stacks which integrate WebKit to render a UI (e.g. guide and storefront) for viewers. We are looking for the best way to identify the supported syntactical elements in each release, such as HTML/CSS tags/properties/values. Eric Seidel's excellent

Re: [webkit-dev] Best way to track feature evolution from release-to-release

2011-01-04 Thread Darin Adler
On Jan 4, 2011, at 1:47 PM, Tom Bahnck wrote: We are looking for the best way to identify the supported syntactical elements in each release, such as HTML/CSS tags/properties/values. Eric Seidel's excellent lecture on the Google code channel points out that the /WebCore/dom/*.idl