Skip to content
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

Merged
merged 254 commits into from
Aug 21, 2024
Merged

Merge tag v2.2.0 into 2.x #1182

merged 254 commits into from
Aug 21, 2024

Conversation

Shadow243
Copy link
Member

@Shadow243 Shadow243 commented Aug 20, 2024

This PR is merging missing commits from tag 'v2.2.0' into 2.x

Shadow243 and others added 30 commits May 6, 2024 20:22
…-doesnot-support-scripts-inclusion

Handled providers that don't permit scripts inclusion
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
…-in-msg-from-backend

Fixed unclosed divs when there are multiple alert messages from backend
Shadow243 and others added 17 commits August 13, 2024 02:35
…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
…ation0-of-dynamic-property-Hm_IMAP--is-deprecated

[FIX] hm-imap.php PHP NOTICE Deprecated:  Creation of dynamic propert…
@Shadow243 Shadow243 marked this pull request as ready for review August 20, 2024 08:35
@Shadow243 Shadow243 requested a review from kroky August 20, 2024 08:38
@Shadow243 Shadow243 changed the title Merge v2.2.0 with 2.x Merge tag v2.2.0 into 2.x Aug 20, 2024
@kroky kroky merged commit b30b176 into cypht-org:2.x Aug 21, 2024
@kroky
Copy link
Member

kroky commented Aug 21, 2024

There seems to be a few more that should also be in 2.x: 2.x...master

@Shadow243
Copy link
Member Author

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.

@marclaporte
Copy link
Member

marclaporte commented Aug 22, 2024

@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

@kroky
Copy link
Member

kroky commented Aug 22, 2024

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.
It might be easier to do the following:

  • develop new features in master
  • fix issues in master
  • be sure to backport these fixes to 2.x branch - it is best at the time of merge or shortly after
  • release 2.2.1, 2.2.2, etc. from 2.x branch (only fixes)
  • release 2.3.0: merge the whole master into 2.x, release from 2.x and tag 2.3.0. Future fixes in 2.x will be released as 2.3.1, 2.3.2, etc. master continues with fixes and features which will later become 2.4.0 or even 3.0.0.

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.

@marclaporte
Copy link
Member

@josaphatim @Shadow243 @Yannick243 @kambereBr @Baraka24 @IrAlfred

Are you OK with this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.