Project:To Do/git

GIT Switch Discussion
So, it looks like Dolphin is switching from svn to git. While this is a purely development decision, it has serious impact on us here at the wiki regarding how we refer to revisions. There is no longer a sequential revision number system that increments with each commit. Love it or not, git is here to stay:

|Forum Topic |Google Code Discussion
 * I specifically asked for a system that continues the existing rev numbers, either by automation or by calling a commit 'revision 77xx'. So far, at least neobrain has expressed his dislike for this idea.
 * This was previously a discussion/flame war about the switch to git. It has since been deleted.

We need to figure out how we're going to deal with not having sequential version numbers. We also need to figure out how we're going to deal with the fact that revision numbers are now very long with no easy way for users to copy/paste the number into a testing or compatibility report.

Based on some light thinking, here are some options:
 * We create/extend a template that will convert from git hex numbers into our own wiki-based rev numbers. This will require a good bit of manual work to update said template, and may possibly get broken as trees are merged and moved around.  I'm not sure I know enough about git's tree and branching system to know if this is a viable option.
 * We stop supporting reports/compatibility for intermediate revs, and focus on the releases / betas / alphas. The devs have indicated that they intend to do more releases in between major versions, so that would certainly help this effort.
 * We convert the existing Template:VersionCompatibility to be a table rather than a bar, with no regard for which release comes before/after other releases.

This is a difficult problem, and one that is either going to require some changes from the devs or some serious rework of the wiki's templates on our part. What are everyone's thoughts?

--Keller999 04:16, 22 August 2011 (CEST)