-
Notifications
You must be signed in to change notification settings - Fork 164
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
Merge tag v2.2.0 into 2.x #1182
Conversation
…-doesnot-support-scripts-inclusion Handled providers that don't permit scripts inclusion
…ve-add-filter Fixed add filter issues
Adapt filter_input_array Hm_Function to return expected _SERVER data in FastCGI as well
Add external resources handling for inline message style
So removing his email. It's better that people come to the chat room.
change the order of options for account creation
…and adjust their appearance to match bs styling used
…attempting-gmail-oauth2-setup [FIX]Error Ocurred when attempting gmail oauth2 setup
…r-name Handle Unicode in folder names
…-in-msg-from-backend Fixed unclosed divs when there are multiple alert messages from backend
…ager Update sieve to latest version
…y_forward_as_message_attachment [ENH] add fonctionality forward as message attachment
…W-translation Add zh-TW Traditional Chinese translation
…integration Fix links when Cypht is embedded
…nese-tests Fix failing tests after adding traditional Chinese translation
Fix left navigation menu toggle buttons
…cant-be-closed [FIX]Some HTML messages can't be closed
… Hm_IMAP:: is deprecated
…ation0-of-dynamic-property-Hm_IMAP--is-deprecated [FIX] hm-imap.php PHP NOTICE Deprecated: Creation of dynamic propert…
There seems to be a few more that should also be in 2.x: 2.x...master |
Maybe this one: e70db0e the rest came after the release. even this last one came after the Docker release. |
@Shadow243 Please update as per https://github.com/cypht-org/cypht/wiki/Lifecycle 2.x should have all of 2.2.0 and all bug fixes from master. But new features can stay in master only and will be released in 2.3.0 |
Hmm, maybe we need some more information on the merging strategy. I thought 2.x is always up to date with fixes and features that would be relased as part of 2.x branch - even 2.3.0. However, I see that might be a challenge backporting all that stuff constantly.
Once we hit a serious update worth bumping to 3.0.0, we can create a 3.x branch from master at that time and stop merging master into 2.x branch. Fixes can still be backported into 2.x branch. I think everything is covered this way. |
@josaphatim @Shadow243 @Yannick243 @kambereBr @Baraka24 @IrAlfred Are you OK with this? |
This PR is merging missing commits from tag 'v2.2.0' into 2.x