Any suggestions are welcome. This the process I think I am going to try to follow for plugin migration, after getting appveyor and travis working and making some progress on it. I am sure others will have their own process and opinions. I am looking for any helpful suggestions to improve this process.
Incidentally, I've found it is not possible to make a PR to a host repository for a "new branch" it is only possible to make a PR into an existing branch in a host repository. So I will only be able to make a PR "ov50" to the host "master" branch for example.
Plugin is Opencpn v4 (ov40)
Changing Plugin from v4 to v5 (ov50)
- Cleanup plugin repository
- Get current with the host repository and get compiling locally.
- Make a new branch and commits as needed.
- Push to your github repository.
- Make a new branch for more commits "compile".
- Add appveyor.yml and .travis.yml
- For appveyor adjust the opencpn.lib downloaded (4.2 or 4.8.2)
- Get both appveyor and .travis working perhaps with more commits.
- Add a Tag for "4.8.2" (as Rasbats did) Later: Actually Rasbats makes a "4.8.2" Branch - very good idea!
- Make a PR "4.8.2" to the host repository.
- Add a Release "4.8.2" version if needed.
- Try to reconfigure cmake to name the plugin ov50
- Is there a particular version number of cmake files that we are supposed to use?
- Change appveyor.yml and travis.yml to ov50 versions.
- Get appveyor and .travis working.
- Make a PR "ov50" to the host repository
- Add a Release "ov50" version if needed.
Thus the plugin will be migrated to ov50 and there will be compiled and Opencpn v4 and v5 plugins will be available on appveyor and travis versions for the next 6 months.
Fortunately a number plug
authors have already moved their plugins forward to "ov50" , so the resultant trail will not be quite the same.
I hope I am not putting myself in some "line of fire" here! This is just my approach, without telling anyone else anything. However I am open to suggestions.