There have been a lot more logistics than I expected getting everything
working. In particular, I miscalculated how much work wix38 needed to work
with all the VS versions. That took time.
Now, I'm slowly working my way through the 8 or so old pull requests.
Migrating to git will not preserve those so I need to work through them and
try to help people get them contributed properly or declined with a good
reason. I'd love to distribute some of that work to make it go faster but I
don't think I can since I have to evaluate the assignment requirements for
each contribution.
So, we are still planning to move to git. More important things are just
not making it happen as quickly as I hoped.
In the meantime, I think we're doing a pretty good job staying on top of
new pull requests (and people are getting assignment agreements signed
before most pull request now which helps a lot). The process Bob laid out
is pretty much it right now. I've done it for about 6-10 changes now so I
know it's possible (and look forward to something better soon as well).
<smile/>
PS: Finishing the evaluation of moving from MSTest to xUnit is behind git
migration as well, so there is plenty of work left to do.
On Thu, Mar 7, 2013 at 10:32 AM, Heath Stewart <hea...@outlook.com> wrote:
> And if I need to make review changes, I have to clone the fork again. A
> few repos adds up and that’s a lot of data (which takes time) to transfer
> across the wire. For the time being I will look into Bruce’s suggestion but
> social coding just seems to work better on Git. Rob talked about moving to
> it and even reflected the common phrase “it won” so like Jacob said: sooner
> would be better than later (especially once more people get involved and
> start forking it).****
>
> ** **
>
> *Heath Stewart*****
>
> VS Pro Deployment Experience, Microsoft
> http://blogs.msdn.com/heaths****
>
> ** **
>
> *From:* Bob Arnson [mailto:b...@joyofsetup.com]
> *Sent:* Thursday, March 7, 2013 8:18 AM
>
> *To:* wix-devs@lists.sourceforge.net
> *Subject:* Re: [WiX-devs] Workflow for pull requests...or, what about Git?
> ****
>
> ** **
>
> On 07-Mar-13 03:06, Heath Stewart wrote:
>
> ****
>
> Exactly the problem. So while I’m working on several changes or even just
> waiting for a pull request to go through while continuing on with other
> chqnges, I have multiple forks and multiple clones. ****
>
> Push to to your fork, delete your clone.
>
>
> ****
>
> That consumes a lot of disk space ****
>
> Each clone is less than 500 MB. Even with SSDs, it's not enough to count
> as "a lot of disk space." Except maybe on a 64GB Surface Pro.<g>
>
> ****
>
> -- ****
>
> sig://boB****
>
> http://joyofsetup.com/****
>
>
>
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> WiX-devs mailing list
> WiX-devs@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-devs
>
>
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
