[racktables-users] RackTables source code switched to git
- From: Denis Ovsienko <infrastation@xxxxxxxxx>
- To: "racktables-users@xxxxxxxxxxxxx" <racktables-users@xxxxxxxxxxxxx>
- Date: Tue, 17 Jul 2012 00:48:16 +0400
Hello, list.
Last year a few RackTables users suggested switching RackTables source code
repository from Subversion to git. Based on the feedback from Alexey, Aaron and
Jonathan I concluded, that this change at that time would harm the project, and
confidently stated, that the switch won't happen really soon.
Now, 8 months later, the switch to git is happening and this time the change is
safe. The team members (including me) have improved their git skills. Alexey
has taken all the care of repository conversion, including development of a
custom conversion script (it is available in racktables-contribs) to make sure,
that all meaningful RackTables development history of the past 5 years is
properly represented in git (a straightforward run of the conversion tool did
not work well for this particular history). Results of his remarkable work are
as follows.
This is the OLD Subversion RackTables repository on SourceForge:
https://sourceforge.net/scm/?type=svn&group_id=293827
The old repository is NOT updated any more since Jul 6 2012, it is being kept
for a historical interest and for scripts, which may be set up to update from
there. The old Subversion repository will be completely removed in a few months.
This is the NEW git RackTables repository on GitHub:
https://github.com/RackTables/racktables
This public repository contains all the history and is routinely updated (feel
free to watch the commits). Next RackTables releases will be made from there.
The current "master" branch stands for Subversion's "trunk" and the current
"maintenance-0.19.x" branch stands for itself.
One of the reasons for the change is making patch contributions more
straightforward, GitHub's "fork and pull request" pattern makes this really
simple (other reasons include trivial backup retrieval, better repository
permissions management and better management of local branches). I have
personally tested this system in other GitHub projects, it works (given that
you have a patch that applies straightforward).
Cheers and thank you for using RackTables!
--
Denis Ovsienko
Other related posts:
