Difference between revisions of "Blender 2.9 Migration"
From URCHN Arkipelago
(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...") |
|||
| (3 intermediate revisions by the same user not shown) | |||
| 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. | '''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: | '''Solution:''' We'll (sorta) follow Subversion's migration strategy: | ||
| − | + | # 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 | ||
| + | # '''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. | ||
| + | # 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/ | ||
Latest revision as of 13:21, 15 July 2020
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.
- create branches/blender29/ in main tube/ folder
- create lib/ and scenes/ in the blender29/ folder
- commit these to Subversion
- 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.
- 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/