Blender 2.9 Migration - Revision history

Bassam at 20:21, 15 July 2020

2020-07-15T20:21:09Z

Bassam at 16:17, 15 July 2020

2020-07-15T16:17:54Z

Bassam at 14:46, 13 July 2020

2020-07-13T14:46:17Z

Bassam at 14:44, 13 July 2020

2020-07-13T14:44:11Z

Bassam: Created page with "'''Problem:''' We need a good strategy to migrate to blender 2.9 without blowing up our checkout (2.7 needs to stay working while we are migrating) and also our repo. '''Solut..."

2020-07-13T14:39:15Z

Created page with "'''Problem:''' We need a good strategy to migrate to blender 2.9 without blowing up our checkout (2.7 needs to stay working while we are migrating) and also our repo. '''Solut..."

New page

'''Problem:''' We need a good strategy to migrate to blender 2.9 without blowing up our checkout (2.7 needs to stay working while we are migrating) and also our repo.
'''Solution:''' We'll (sorta) follow Subversion's migration strategy:
* the two main folders to migrate are lib/ and scenes/ in the main project folder.

@@ Line 1: / Line 1: @@
 '''Problem:''' We need a good strategy to migrate to blender 2.9 without blowing up our checkout (2.7 needs to stay working while we are migrating) and also our repo.
 '''Solution:''' We'll (sorta) follow Subversion's migration strategy:
-* the two main folders to migrate are lib/ and scenes/ in the main project folder.
+# the two main folders to migrate are lib/ and scenes/ in the main project folder.
-* create branches/blender29/ in main tube/ folder
+# create branches/blender29/ in main tube/ folder
-* create lib/ and scenes/ in the blender29/ folder
+# create lib/ and scenes/ in the blender29/ folder
-* commit these to Subversion
+# commit these to Subversion
-* '''copy or move (windows) or symlink (linux) lib/maps and lib/maps_low if needed/'''
+# '''copy or move (windows) or symlink (linux) lib/maps and lib/maps_low if needed/'''
-* replicate the rest of the folder structures under lib/ and scenes/ (excluding the existing *28/ ) folders and commit these to subversion
+# replicate the rest of the folder structures under lib/ and scenes/ (excluding the existing *28/ ) folders and commit these to subversion
-* Create a new addon that is a combination of the old sparkleshart and migrate28, that uses svn copy to duplicate the files, and then migration heuristics to change those files.
+# Create a new addon that is a combination of the old sparkleshart and migrate28, that uses svn copy to duplicate the files, and then migration heuristics to change those files.
-* Manually check, copying/ changing if needed
+# Manually check, copying/ changing if needed
-* Commit new files
+# Commit new files
 Much later:
 * SVN delete the old lib/ and scenes/ file
 * SVN rename the folders to switch branches/blender29/ to main/

@@ Line 5: / Line 5: @@
 * create lib/ and scenes/ in the blender29/ folder
 * commit these to Subversion
-* '''copy or move (windows) or symlink (linux) lib/textures/'''
+* '''copy or move (windows) or symlink (linux) lib/maps and lib/maps_low if needed/'''
 * replicate the rest of the folder structures under lib/ and scenes/ (excluding the existing *28/ ) folders and commit these to subversion
 * Create a new addon that is a combination of the old sparkleshart and migrate28, that uses svn copy to duplicate the files, and then migration heuristics to change those files.

@@ Line 5: / Line 5: @@
 * create lib/ and scenes/ in the blender29/ folder
 * commit these to Subversion
-* replicate folder structures under lib/ and scenes/ (excluding the existing *28/ ) folders and commit these to subversion
+* '''copy or move (windows) or symlink (linux) lib/textures/'''
 * Create a new addon that is a combination of the old sparkleshart and migrate28, that uses svn copy to duplicate the files, and then migration heuristics to change those files.
 * Manually check, copying/ changing if needed

← Older revision		Revision as of 14:44, 13 July 2020
Line 2:		Line 2:
	'''Solution:''' We'll (sorta) follow Subversion's migration strategy:		'''Solution:''' We'll (sorta) follow Subversion's migration strategy:
	* the two main folders to migrate are lib/ and scenes/ in the main project folder.		* the two main folders to migrate are lib/ and scenes/ in the main project folder.
		+	* create branches/blender29/ in main tube/ folder
		+	* create lib/ and scenes/ in the blender29/ folder
		+	* commit these to Subversion
		+	* replicate folder structures under lib/ and scenes/ (excluding the existing *28/ ) folders and commit these to subversion
		+	* Create a new addon that is a combination of the old sparkleshart and migrate28, that uses svn copy to duplicate the files, and then migration heuristics to change those files.
		+	* Manually check, copying/ changing if needed
		+	* Commit new files
		+
		+	Much later:
		+	* SVN delete the old lib/ and scenes/ file
		+	* SVN rename the folders to switch branches/blender29/ to main/