RFC: workingdir

[Bill Barry]

Steve Borho wrote:
> On Mon, Jun 7, 2010 at 9:00 AM, Dirkjan Ochtman <dirkjan at ochtman.nl> wrote:
>   
>> On Mon, Jun 7, 2010 at 15:46, Greg Ward <greg-hg at gerg.ca> wrote:
>>     
>>> Hmmm.  One thing at a time.  This is going to cause pain for extension
>>> authors.  (It's not that adapting any single extension will be that
>>> hard, but I bet many many extensions will break.)  I think the painful
>>> changesets should have some space between them so we can adjust to one
>>> change at a time.  I don't know if there should be so much space
>>> between them that Mercurial 1.6 fits in between: i.e. should we factor
>>> out workingdir in 1.6 and then cleanup hg.py in 1.7?  Worth
>>> considering.
>>>       
>> I'm kind of meh on spacing out the API breakage. In fact, I tend to
>> think that it's better if we have lots of breakage in 1.6 and none (or
>> very little) in 1.7 then having some in the first and some in the
>> other; especially if the breakage is related, I think breaking
>> everything at once is probably easier on the extension authors than
>> spreading it out.
>>     
>
> +1 on ripping off the bandage all at once.
>
>   

+1 for doing this all at once, but not for the purpose of only breaking 
the API once, instead because doing so allows faster progressive change. 
The API will likely break again for other reasons at 1.7 (though 
probably not such a large break). As an extension author I knew this 
going in.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100608/809dab1f/attachment.htm>