Thanks. Bob and I don't purposefully make decisions to make other's lives
difficult but sometimes we miss obvious things that could be done better. So I
always try to ask, especially when it will *break* everyone out there. <smile/>
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Thursday, February 6, 2014 2:00 PM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] The Great GitHub Discussion
Just listened to the github discussion, my initial thought is "don't care!" -
by that I mean most of the discussion focuses around what you (Rob, Bob) need
for managing the code/releases, from a dev viewpoint it is a repository we just
use it, if our lives are easier it is good but not essential. Given that I
would say if the managers of the code need/prefer it, go for it.
(May be I am saying this because in my day job I am your side of the fence and
want my life to be easy.)
Neil
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 06 February 2014 18:52
To: WiX toolset developer mailing list
Subject: [WiX-devs] The Great GitHub Discussion
In today's WiX Online Meeting http://youtu.be/4QlCTgmS33Y (about minute 10) I
spent about 15 minutes talking about the reasons to move to GitHub. At this
point, I believe it is inevitable that we will move the question is when and
what it should look like when we move.
First, in the move we'll be breaking history. We'll start from scratch to clean
up our messy history and get the crazy whitespace issues all sorted out (the
problem driving this move). That means when we do this, you'll have to go to a
different repo to go fully back in time. Keep that in mind reading on.
When.
When do you think we should move? Should we go now in the middle of v3.9 and
v4.0? Should we wait to move when each next version (v3.10 and v4.1) is ready
to start?
I already have a couple votes (thank you Blair and Bruce) for moving basically
now. I'm looking for more opinions. Even if your opinion is "It doesn't matter
to me." Voting helps me get a good idea what people want.
What.
As mentioned in the Online Meeting (if you haven't listened yet, please do),
GitHub provides a few new degrees of freedom. The biggest is that we have an
"umbrella organization" that can own multiple repositories. Today, on CodePlex,
we have to squish all of our stuff into a single repository which is
unfortunate. Some examples what GitHub would allow us to do:
1. Create a repo for the "website". I think this is a pretty obvious move
and will make it clearer where to go to improve content on
http://wixtoolset.org/.
2. Create a repo per major version of WiX toolset. In other words, there
would be "wix3" and "wix4" repos. This would allow us to use "master" branch
correctly (wix3 repo master branch would hold v3.8) and "develop" branch (wix3
repo develop branch would hold v3.9). That sounds great to me but there is a
downside. You'd no longer be able to have one repo on disk and switch between
all versions of the WiX toolset. Personally, I don't work that way anyway (I
have separate folders with wix39 and wix40 on my machine) but it's something we
should discuss here.
Anyway, please vote for when and if you have thoughts on how to organize our
code in GitHub let's discuss them.
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
