Plugins using wxWidgets 3.1.1

[Rasbats]

Is there an easy naming policy to distinguish plugins built with wxWidgets 3.11.

Do I need to make a new GitHub repository for each 3.1.1 plugin to avoid confusion?

wxGrid has needed some big changes to source code to accomodate wxWidgets 3.1.1. There will probably be others.

Mike

[bdbcat]

Mike,,,

Probably best to create new branches in the same repo for the 3.1.1 updates. That way we keep full history in one spot.

Dave

[Rasbats]

Dave ...

But this is opposite from how you are using branches for OpenCPN on GitHub. Should the Master have the latest 3.1.1 code, leaving a branch with the old code.

Ok, and do I give the plugin a new version number to reflect the use of wxWidgets 3.1.1?

The opencpn.org plugin page could point to the release for the relevant version.

Mike

[nohal]

Mike...
The standard way to do this is to start new development in a new branch, then, when that matures merge it to master and, if needed, have another branch created at the same point to fix bugs in the older generation.
You should give the plugin a new version number with every release. With this change, I would probably increase the major version to point out that there is a break in compatibility.

Pavel

[bdbcat]

Mike...
I agree with Nohal.

To reiterate:
You will see a branch "o486" in the OpenCPN github repo. That branch was captured at the point of release of 4.8.6. It will build the current production release, and will be forked again to contain critical backports if required. New work goes on in "master".

The opencpn.org download page will generally point to "master" of the plugin repo for the source link. Presumably source builders will know which branch they need to pull for local builds. The download page will also point to built binaries that are compatible with the current release of base OCPN, whatever that may be at the time.

If/when we have a Beta underway that breaks compatibility, there will be another section of the .org site that provides links to plugin Beta binaries ready and available for test with the Beta base.

Dave

[Rasbats]

Dave, Nohal ...

Thanks for the policy discussion. I will start implementing this for the plugin stuff I have on GitHub.

Mike