[oi-dev] Git as a version control system for new OI projects

[Bayard Bell]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Garrett,

I may be making a huge leap here, but I had some expectation that the tools issue are navigable if Joyent's been using git (I'll immediately concede that there are all kinds of ways I might be wrong about that). I don't mean to diminish the question of toolchain transition issues across SCMs, but I think there's a thought process that's not just "ooh, shiny" underlying the suggestion to move to git, which should be foregrounded.

As you rightly say, there's a viability threshold that has to be passed or cleared, but if that's sorted, I think the questions shift from what needs to be supported by integration with the existing toolchain to understanding how branching and such are supposed to work as processes, what of that isn't already integrated into the toolchain (i.e. because that's direct interaction with the SCM), and whether there's a substantial improvement in implementing that workflow with a particular SCM. The problems we've got with things like MQ are encountered precisely where the toolchain ends and people discover that operations they have to perform in the SCM are a bit of a hole in the head. It could be that we're underutilising Mercurial, whether in its core feature set or its extensions, and it would definitely help evaluate that if the use cases and our understanding of the issues were spelled out.

I don't think we get to the right answer without having both workflow/process and existing integration points on the table, but we may never get to any question about toolset integration if we are clear about the former.

Cheers,
Bayard

On 22 Jun 2011, at 18:50, Garrett D'Amore wrote:

> My biggest concerns about switching to git really relate to tooling.  If
> the tools can all accommodate git, then I don't really care.  
> 
> 	- Garrett
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.12 (Darwin)

iQIcBAEBAgAGBQJOAlQHAAoJEHm5cBpJ87doPCcP/R9QLEsyH3grauLGTaVChXgv
MuxrE5Edrvj1bsWKYFDLMRMtnYciQr2VAAnkVV9efO8Afs1W8OrUqiL425/qwG3O
VHvyG6B6kxoJifhmLEGcGFPcQt8oViULCPRrCHjs3l9V9T8onRhKPnfUe7pxKk3U
T0neL8gYkI4OmGOB691n6ulojZ9s0sMrVT+FidIokq/WR9vyUJDoohec1gz3F68/
F10xwA4n+oSAZzoIPuwofw+JSrqnUEVoXl7ws0YHftx4Tkhe7RQ9i+loyqgGNuRo
4IJzLdiZibNw61yk8Sxkt/+IMDWIamYAx4lwrOTrjI4UjG14IptMgW8kHMwXgF3U
ZVavU2QNv7L+1Qu63p5hnXePSuzVrMJxZZ3qTUAfKwMEScgpdXPeYGA0L1K39qfF
npnha7aQCILzxXXyjHntTVtvGR3ezE9KWis1YPxcZKciQp7a9VNTwDSl0ytWw4nR
BhVQJJIK0M8bp9tHB2v52avZi4Cxc+aNQN97S2j6bY6egc9p3sSvikxBQMMpUfUX
kCssNvfqtgHzDkXgXOVTI40uFqXVOLEHwMkn2PrPqSFI/PTM0jDlEjExhR6ulh8o
jNZGDNveKOFt+vAccTo5mTJ9Dfz08Q8jYnLnVcj4H159SLkCt9MFse4CzrYnFWd0
LIRpF7ED66eF9bJYkO54
=hh/6
-----END PGP SIGNATURE-----