best practices to update project to 2022 from 2021. Duplicate and new repository?

Target Platforms XR
1

hi all,

Super noob here, can someone point me in a direction to understand better how I should be duplicating a project to create a clean copy that I can work on in a new version of Unity?

I want to start to port over a project from 2021 to 2022 so I can begin to prep it for Apple Vision Pro, but I don’t want to run the risk of messing up the primary project.

So I figured I’d duplicate the project, and then create a new apple ID, and a new plastic repository, etc, but when I try opening the duplicated project, it still automatically links to the old repository.

Is this actually something I should be trying to do with creating a branch of a repository that I would work on in 2022? It feels like it would be cleaner to just have an entirely separate project with a separate repository, etc.

Not sure if this is the right forum but appreciate any guidance you have – I’ve tried googling and can’t quite get it sorted.

Thanks!

2

Hi @RoryMercantile

There should be no need to duplicate projects in this way. As you mentioned, you should utilise branches in a\your source control solution.

I can’t speak for Plastic SCM (I use GitHub \ GitHub Desktop here) but in GitHub you would create a feature branch (off of your main branch)

This might be called (for example) unity2022upgrade and the upgrade would take place using that branch. Once complete, you can merge your changes back to the main branch and delete the unity2022upgrade branch.

Understanding the features that a good source control solution offers does require an up-front time investment, but it will pay off in no time at all.

Good luck!