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

Darin Fisher darin at chromium.org
Fri Jan 7 09:24:42 PST 2011

On Fri, Jan 7, 2011 at 9:12 AM, Ojan Vafai <ojan at chromium.org> wrote:

> 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.
> Ojan

Totally agree.  We probably just need some kind of dotted notation to handle
branches.  The WebKit trunk should just increment N in "N.0", and then
branches can increment the minor number.

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

More information about the webkit-dev mailing list