Changes between Initial Version and Version 1 of MoveToGitHub

Timestamp:

Mar 20, 2012, 3:46:59 AM (12 years ago)

Author:

heikki

Comment:

--

MoveToGitHub

@@ +1 @@
+= Move to GitHub =
+
+|| '''Date''' || 2012/03/20 ||
+|| '''Contact(s)''' || Heikki Doeleman ||
+|| '''Status''' || proposed ||
+|| '''Assigned to release''' || 2.7 ||
+|| '''Resources''' ||  ||
+
+== Overview ==
+
+Using SVN on Sourceforge is not very optimal for version control. Especially if you do larger commits, it very often fails, which requires that you do all sort of things to get your local copy back in a 'fit' state before trying again. A large commit last week took me 3 hours to complete, having had to split it up in dozens of smaller commits. This is an unacceptable amount of time and it also pollutes version control history as it should have been a single, logical, atomic commit.
+
+This proposal aims to try out [https://github.com/ | GitHub] for a trial, and if we're satisfied, move permanently to that.
+
+  
+=== Proposal Type ===
+ * '''Type''': Version Control Change
+ * '''App''': !GeoNetwork
+ * '''Module''': all
+
+=== Voting History ===
+ * Vote proposed: 
+
+----
+
+== Motivations ==
+
+To find out whether this move is really advantageous I propose we cope trunk to Git and then use a trial period of say 2 weeks or 1 month during which all developers should commit to both Git and SVN. At the end of this period the developers should decide whether to move permanently or not.
+
+When moving permanently, the night build script, Hudson and the web site need to be updated.
+
+
+
+
+=== Backwards Compatibility Issues ===
+
+When we permanently move, SVN wil no longer be updated so links and docs about using it will be out of date.
+
+=== New libraries added ===
+
+None.
+
+== Risks ==
+
+Everything is risky..
+
+== Participants ==
+ * all !GeoNetwork developers