- From: James Graham <jgraham@opera.com>
- Date: Tue, 22 Jan 2013 12:54:19 +0100
- To: public-webapps@w3.org
On 01/22/2013 12:37 PM, Anne van Kesteren wrote: > On Tue, Jan 22, 2013 at 12:30 PM, Tobie Langel <tobie@fb.com> wrote: >> That's definitely something to keep in mind. How frequent is it that a >> feature moves from one spec to another (that, is outside of the continuous >> flow of features that migrate from HTML5 to WebApps)? >> >> Is your concern about history loss? > > My concern is 1) make work and 2) overhead of deciding what has to be > tested where. E.g. tests for the ProgressEvent interface test quite a > bit of IDL related requirements, where do they go? From a distance it > might all appear modular, but it really is all quite interconnected > and by creating artificial boundaries that interconnectedness might > not get testing. I don't have a strong opinion either way here, but I note that it is generally possible to move things between repos relatively easily without losing history e.g. using git subtree[1], so I don't think that it is necessary to make a decision on this before moving to git. With that in mind, I suggest doing the move with the repository structure more or less as it is today and then later merging the repos if we decide that is desirable. [1] https://github.com/apenwarr/git-subtree/blob/master/git-subtree.txt
Received on Tuesday, 22 January 2013 11:54:49 UTC