Differences

This shows you the differences between two versions of the page.

--- developers:git:switch_to_git [2017/05/03 14:52] – ↷ Links adapted because of a move operation Jean-Michel Beuken
+++ developers:git:switch_to_git [2017/06/14 11:38] – [Introduction] Xavier Gonze
@@ Line 1: / Line 1: @@
-====== Switch from Bazaar to Git : the ABINIT developer path ======
+====== ABINIT developer path to Git ======
 ===== Introduction =====
@@ Line 6: / Line 6: @@
 By contrast, [[https://git-scm.com/|git]] shows advantages with respect to other VCS, in particular, an impressive speed, thanks to its commit storage model. See [[https://en.wikipedia.org/wiki/Git_%28software%29|Wikipedia]]: "The Eclipse Foundation reported <...> that as of May 2014, Git is now the most widely used source code management tool, with 42.9% of professional software developers reporting that they use Git as their primary source control system”.
-So, after consulting the most active developers of the ABINIT community, the decision has been taken to switch to git.
+So, after consulting the most active developers of the ABINIT community, the decision has been taken in 2015 to switch to git.
-===== How will this be organized ? =====
+(Related doc : [[maintainers:blueprints:gitlab_specs]]).
-The switch is organized in three phases :
-  - Definition of the future ABINIT development model (this phase is now finished).
-  - Set up of the needed scripts, while in the meantime the ABINIT developer community is asked to learn about git and the future working mode.
-  - One specific, agreed, day, bzr is abandoned, and git replaces bzr. Everybody starts to work on git. There is no way to make a smoother transition...
-===== What should I do ?  =====
+===== What should I do to jump in ?  =====
-It will take a few hours to learn about git and the future ABINIT development model.
+It will take a few hours to learn git and the corresponding ABINIT development model.
-  * First step : become familiarized with the basics of git. This means simply to read chapters 1 to 3 of the "Reference Manual" of git, that is available at [[https://git-scm.com/doc]]. Install a version of git on your local development computer, and play a bit with it. This will likely take two hours.
+  * First step : become familiarized with the basics of git. This means simply: read chapters 1 to 3 of the "Reference Manual" of git, that is available at [[https://git-scm.com/doc]]. Install a version of git on your local development computer, and play a bit with it. This will likely take two hours.
-  * Second step : become familiarized with the so-called [[http://nvie.com/posts/a-successful-git-branching-model|gitflow]]. Indeed, the working mode that will be adopted is quite close to this flow (see later).
+  * Second step : become familiarized with the so-called [[http://nvie.com/posts/a-successful-git-branching-model|gitflow]]. Indeed, the working mode that is adopted for ABINIT is quite close to this flow (see later).
   * Third step : spend some time to get familiarized with gitlab. in particular, please, log in on   page [[https://gitlab.abinit.org]]. In order to do this, you have first to arrange an access with Jean-Michel Beuken (jean-michel.beuken@uclouvain.be) : send him an e-mail and he will create for you an SSH access.
   * Fourth step, read [[developers:git:specificities_git_abinit#standard_names_projects_branches|the specificities of the use of git for the ABINIT project]].
   * Fifth step : you might have a look at the [[maintainers:blueprints:gitlab_specs|blueprint from Yann, entitled "Gitlab specifications"]].
-  * Sixth step : continue to practice while waiting the phase 3 switch !
+  * Sixth step : practice !