[webkit-dev] Best way to track feature evolution from release-to-release
ojan at chromium.org
Fri Jan 7 09:30:51 PST 2011
On Fri, Jan 7, 2011 at 9:24 AM, Darin Fisher <darin at chromium.org> wrote:
> On Fri, Jan 7, 2011 at 9:12 AM, Ojan Vafai <ojan at 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 it is better in general than developers using the individual
>> products' version numbers.
> 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.
The branches are not cross-port though, right? We already have individual
product numbers in the UA string that meet this need (e.g. the Chrome or
Safari version number).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev