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

Ojan Vafai ojan at chromium.org
Fri Jan 7 09:12:29 PST 2011

On Thu, Jan 6, 2011 at 8:57 PM, Ryosuke Niwa <ryosuke.niwa at gmail.com> wrote:

> On Thu, Jan 6, 2011 at 8:31 PM, Darin Fisher <darin at 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
>> branch for instance.  So, you cannot do simple "if version > N" checks to
>> test for the availability of features.
> 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.

Right. Having a shared version number across WebKit builds will never catch
every case (e.g. patches pulled into branches, disabled features, etc.), but
it is better in general than developers using the individual products'
version numbers.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20110107/6d3e6be2/attachment.html>

More information about the webkit-dev mailing list