W3C home > Mailing lists > Public > public-browser-tools-testing@w3.org > January to March 2012

Re: Browser Automation API spec

From: James Graham <jgraham@opera.com>
Date: Mon, 2 Jan 2012 20:48:32 +0100 (CET)
To: Simon Stewart <shs@google.com>
cc: public-browser-tools-testing@w3.org
Message-ID: <alpine.DEB.2.00.1201022042420.15227@sirius>


On Fri, 30 Dec 2011, Simon Stewart wrote:

> Hi, I'm a big fan of doing as much work as possible out in the open, and 
> I'm more than happy to work on the WebDriver spec that way too, but I 
> thought I'd approach the list about the preferred style of development 
> before committing anything to the hg repo.
> 
> As I see it, the options are:
> 
> 1) Keep the repo as close to stable as possible. This will mean fewer 
> but larger checkins, but anyone using the spec that's in there has the 
> appearance of stability.
> 
> 2) Check in frequently and often. This will mean more, smaller checkins, 
> and anyone attempting to use the spec might find the ground shifting a 
> little.

>From experience with other specs, option 2) is much better. It puts you in 
a position where looking at the spec on a random day gives you a closer 
approximaion to the final spec than the "occasional large update" model. 
It also means that everyone has access to the same information and can see 
the current thinking of the editor. For these reasons, I strongly 
recommend going with a model where you check in and push every coherent 
edit that you make.
Received on Monday, 2 January 2012 19:49:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 2 January 2012 19:49:11 GMT