I am working on a huge project (“project”), which is open source, and I am changing the project, but I do not have permission to complete it. I am looking for strategies to support my own project branch. Some issues that I consider:
- How to put my own work in the version control system, given that I change the source code of the project, adding new files, etc.
- How to keep synchronization with the project without the need to re-merge your own changes again and again.
I have never been in this situation - I always supported my complete project in some version control system. My plan right now looks something like this:
- Creating a directory tree in my SVN, similar to what was in the project.
- Saving all modified files (and only them) in my svn.
- Each time I decide to synchronize with a new project database, I will do a check, merge my SVN tree into a new version, test it, and then transfer my changes to my SVN and distribute them along with the last project to the base level.
The problems are here. END. Too many manual steps, more and more work with time, etc. The right way to go, of course, will be part of the original project, but right now it doesn’t matter in different ways, and that’s out of the question.
Ideas?
source
share