-
Notifications
You must be signed in to change notification settings - Fork 979
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
Enable group chats in release build #6882
Comments
@cammellos could you share your thoughts on what's needed to release the group chats? Is the core work already done? |
@lukaszfryc if no blocker have been reported, I would just want to push out a couple of commits to fortify the implementation but otherwise we are good to go. What do you reckon? |
@cammellos Whilst on the topic can you outline the PFS release plan too? |
So, if no issues have been reported on group chats & pairing, I think we can start thinking about releasing PFS and getting things ready.
Enabling PFS for 1-to-1 will be a breaking change, but if we release group chats (or pairing, or both ) next week, those clients will be already compatible, so it will give us a bit more time for users to upgrade, making the upgrade less painful.
|
@cammellos there are no blockers. Only issues we already discussed that can be fixed later. Re releasing group chats in dev mode, I don't think anyone will use them this way. So, we will not learn anything besides just having the code enabled in the release build. I'd suggest to enable them in normal mode for nightlies and include in the next release. @cammellos? |
@lukaszfryc I am ok with that, the only reason to have them in dev mode would be to warn users that is a beta-feature. So as long as we warn users that is a beta feature, I am ok in having them always on, in order to manage expectations. |
What about pairing, should we do the same? release it I mean? The only thing I would want to add is a way for the user to name its device, but other than that if no issues/blockers I'd be happy to release |
+1 for rolling this out. We can be sure to communicate to users this is an early feature and testing and feedback is appreciated. |
If we still consider it a beta-feature, it makes sense to put it under dev mode. I think it's the best way to indicate (inside the app) that something is a beta feature. |
@lukaszfryc what about something like: |
Note, the whole app is in beta! Every feature is a beta :) But it won't hurt doing |
Hm, I first thought that "dev mode" is for beta-features. But, we can actually differentiate between "options for developers" (dev mode) and beta features.
Yeah. I'd say that if there is no major issue that we want to warn about, I'd not bother users with "Beta" word in yet another place. |
@churik I see we have some "pairing" issues that are leftovers after #6697. Is any of them a blocker for releasing the pairing in current state? |
ok, in any cases, we are all in agreement about releasing next week, when are we cutting the release branch these days? sometimes early next week? just to get things organized |
@cammellos let's discuss it in #6891 |
@churik so you mean we can release pairing? Btw, for group chats, we are planning to use "Start group chat (Beta)" to indicate that it is a beta-feature. Do you think we should do the same for "Devices (Beta)"? |
According to #6891, the release branch will be created today. @cammellos could you go ahead and enable group chats in release builds? As for pairing, I still think we should improve on UX there (see #6898 (comment)). At least update copies. But if we do not have time, we may include it in the release and see if someone will use it. |
@lukaszfryc I think it should be under development mode, as this feature is still WIP. |
@cammellos I updated description of this issue and assigned it to you. |
group chats and pairing were enabled in dd21f6a |
Awesome! |
Enable group chats and pairing in release builds and cherry pick it into release/0.9.32 branch. Both features should remain under development mode.
Please update release changelog afterwards https://notes.status.im/mobile-release-notes?both
The text was updated successfully, but these errors were encountered: