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

Ryosuke Niwa rniwa at webkit.org
Thu Jan 6 20:58:11 PST 2011

On Thu, Jan 6, 2011 at 8:31 PM, Darin Fisher <darin at chromium.org> wrote:

> On Thu, Jan 6, 2011 at 4:39 PM, Ojan Vafai <ojan at chromium.org> wrote:
>> Some ideas:
>> -Use the svn revision number. That has the downside of being tied to SVN
>> should we want to change version control systems.
>> -Have a file checked in that corresponds to the WebKit "version" at that
>> revision. Any port is allowed to increment the number in that file whenever
>> they please. It's monotonically increasing, not tied to a given version
>> control system or to an individual port's release process.
>> Ojan
> 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 branch
> for instance.  So, you cannot do simple "if version > N" checks to test for
> the availability of features.
> -Darin

I think Ojan meant that the version number can be used to learn about
bugs such as crashes and incompatibilities that have been fixed but cannot
be detected as a feature.

- Ryosuke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20110106/27150d1a/attachment.html>

More information about the webkit-dev mailing list