Changes between Version 48 and Version 49 of GitMigration

Timestamp:

May 17, 2019, 2:32:10 AM (5 years ago)

Author:

neteler

Comment:

Migration has been started as of 17 May 2019

GitMigration

@@ -134 +134 @@
 == Implementation of migration from OSGeo SVN and trac to !GitHub ==
 
-=== Migration plan (draft) ===
-
-Two possible scenarios below. Similar procedure will be launched for `grass-addons` repo.
-
-==== Scenario 1 (source code + issues in one step) ====
-
-(whole procedure will take few hours, not more then one working day)
-
-1. migration of source code and issues will be announced on grass-dev ML few days before day D
-2. svn and trac ticket system (only tickets, wiki will be still editable) will be switched to read-only mode
-3. git `grass` repo (https://github.com/grass-svn2git/grass) will be created from scratch and switched to private mode 
-4. source code migration will be launched (https://trac.osgeo.org/grass/browser#grass-addons/tools/svn2git; will take 1-2 hours)
-5. meanwhile migration of trac issue will be launched (target: `grass` repo; will take few hours)
-6. switch `grass` repo to public mode
-7. move `grass` repo under [https://github.com/OSGeo/ Github OSGeo organization]
+=== Migration plan (in action) ===
+
+~~Two possible scenarios below.~~ Similar procedure will be launched for `grass-addons` repo.
+
+**Migration has been started as of 17 May 2019!**
+
+==== ~~Scenario 1 (source code + issues in one step)~~ ====
+
+~~(whole procedure will take few hours, not more then one working day)
+
+~~1. migration of source code and issues will be announced on grass-dev ML few days before day D~~
+~~2. svn and trac ticket system (only tickets, wiki will be still editable) will be switched to read-only mode~~
+~~3. git `grass` repo (https://github.com/grass-svn2git/grass) will be created from scratch and switched to private mode~~
+~~4. source code migration will be launched (https://trac.osgeo.org/grass/browser#grass-addons/tools/svn2git; will take 1-2 hours)~~
+~~5. meanwhile migration of trac issue will be launched (target: `grass` repo; will take few hours)~~
+~~6. switch `grass` repo to public mode~~
+~~7. move `grass` repo under [https://github.com/OSGeo/ Github OSGeo organization]~~
 
 ==== Scenario 2 (two steps) ====
 
-1. source code migration
- 1. migration of source code will be announced on grass-dev ML few days before day D
- 2. svn system will be switched to read-only mode
- 3. Git `grass` repo (https://github.com/grass-svn2git/grass) will be created from scratch
+1. source code migration - **started as of 17 May 2019**
+ 1. migration of source code will be announced on grass-dev ML few days before day D - [x]
+ 2. svn system will be switched to read-only mode - [x]
+ 3. Git `grass` repo (https://github.com/grass-svn2git/grass) will be created from scratch - WIP
  4. source code migration will be launched (https://trac.osgeo.org/grass/browser#grass-addons/tools/svn2git; will take 1-2 hours)
  5. move `grass` repo under [https://github.com/OSGeo/ Github OSGeo organization]
-2. trac ticket migration
- 1. migration of issues will be announced on grass-dev ML few days before day D
+ 6. switch `grass` repo to public mode, ready to receive commits.
+2. trac ticket migration - planned for 18/19 May 2019
+ 1. migration of issues will be announced on grass-dev ML few days before day D - [x]
  2. trac ticket system (only tickets, wiki will be still editable) will be switched to read-only mode
  3. git `grass` repository under OSGeo organization will be switched to private mode
  4. migration of trac issue will be launched (target: `grass` repo; will take few hours)
- 5. switch `grass` repo to public mode
+ 5. switch `grass` repo back to public mode
+
 === Transfer to repo to OSGeo organization within !GitHub ===
 
-One option is to update the existing draft migration (https://github.com/grass-svn2git/) uner the existing OSGeo organization on !GitHub:
+One option is to update the existing draft migration (https://github.com/grass-svn2git/) under the existing OSGeo organization on !GitHub:
  * https://help.github.com/en/articles/transferring-a-repository
 
@@ -180 +184 @@
 
 Updating is always possible and easy, so nothing is lost.
+
 === Needed source code updates ===
 
@@ -193 +198 @@
   * Issue labels:
    * draft: https://github.com/landam/grass-gis-git-migration-test/labels
+
 ===  New labels in the !GitHub issue tracker ===
   * c.f. also current QGIS cleanup "Migrating issues from Redmine to GitHub"
@@ -209 +215 @@
 
   * https://git.osgeo.org/gitea
+
 == Future plans not being part of initial migration ==