-
Notifications
You must be signed in to change notification settings - Fork 150
V4.9.2 #1206
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: v4.x
Are you sure you want to change the base?
Conversation
@twothreenine @lentschi FYI: see #1199 (comment) and onwards on the juggling of branches. |
Added @robwa too, if you are able 😁 |
EDIT: Ah, sorry - just saw, that you're cherry-picking from 4.x, but still: Haven't these changes been reviewed elsewhere and if so, how can we find the reviews to check if the cherry-picks could cause trouble in this case? |
Cherry picking is done separately. I am reviewing those as we speak 😁 As soon as I re-push that branch, I encountered an issue, I will add the commits as well. Only a few but some do bother the FCAN users at this time. As long as v4 is not abandonded adding (minor) improvements is not a bad thing, in my book anyway. Part of the fixing/improving here was also meant as a way to get a bit better acquinted with the code. It is not imperative but does provide a few minor tweaks. I did find an issue yesterday, I left a Mollie specific item in there by accident, which I am going to address soon. Again also part of me getting to understand the plugin idea a bit better. As a side note: while cleaning up the release4 confusion I also killed the |
Bumped to 4.9.2
Note: merging to main release branch/trunk for future
v4.x
releases.