<br><br><div class="gmail_quote">On Fri, Jun 25, 2010 at 2:14 PM, David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
On Fri, Jun 25, 2010 at 11:18:19AM +0200, Bert Freudenberg wrote:<br>
><br>
> So I'm strongly in favor of switching to a DCVS. I personally only ever<br>
> used git, but since hg supposedly has better x-platform support that<br>
> would be fine too (the Windows devs should speak up). Wouldn't be<br>
> opposed to bzr either.<br>
><br>
<br>
</div>I don't know if this is a good idea or not, but I have to say that<br>
right now would be a poor time to consider major changes to the<br>
infrastructure unless there is a *truly* compelling reason to<br>
do so. </blockquote><div><br></div><div><br></div><div>I think the opposite :) It's a wonderful opportunity to learn. When I started working on the Linux kernel, I've learned a lot because all patches go through the Linux Kernel Mailing List (thanks to Git), discussed, reviewed, integrated in experimental branches and finally in official one.</div>
<div><br></div><div>A real force of Git infrastructure is to bring visibility. Cog is here, let's learn, play and contribute easily.</div><div><br></div><div>Cheers,</div><div><br></div><div>Laurent</div><div><br></div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">The reason is managing change overall - the Cog development<br>
represents a huge opportunity, but it also implies a lot of new<br>
things to understand and integrate, and new work to be done by<br>
folks who will need to understand the changes. Performing a<br>
simultanious migration to new version control and build processes<br>
would likely lead to delays and disruption in the more important<br>
objective of making progress on the VM.<br>
<br>
I suggest that we focus on successful integration of Cog this year,<br>
and consider moving to some new version control infrastructure at<br>
a time when we are sailing on calmer waters.<br>
<br>
Dave<br>
<br>
</blockquote></div><br>