-
Notifications
You must be signed in to change notification settings - Fork 2
feat: 0.4.0 for GitExtensions 6.0 #33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
I don't know, tbh. It doesn't look like there are any coupling to a specific version of GE. |
I now realizes what this does, it packages GitExtensions.Extensibility from master. Some plugins uses [0.3-0.4) Maybe including the following too? |
Sounds good |
The coupling is in https://github.com/gitextensions/gitextensions.pluginmanager/blob/master/src/GitExtensions.PluginManager/Plugin.cs#L55. The idea is that by selecting minimal version, we limit plugins targeting the version. In other words, ideally we should SemVer (or to simplify things follow Git Extensions version) this package to be able to filter-out plugin targeting older, possibly incompatible, version of Git Extensions |
If 6.0 is next major release, we should bump this package to |
There were no update at all for GE5 and there are quite few changes in GE6. So apps that use 0.3 often works. At least Gerrit plugin will require a recompile with new version. |
The PRs in milestone for 6.0.0 is now merged, this should be merged so plugins can be prepared |
If Git Extensions V6 are "backward compatible" with existing plugins, we don't need to bump anything. |
GE 5 did more changes, but the ext version was not changed. No reported problems. It depends on the plugins how the change hits them. I would assume most are compatible with GE4/GE5. If ext version is changed they could stop working. But we could set version to 0.4 and require plugin updates. |
I agree with 0.4 |
Is this needed for plugins?