-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Clarify upgrade notes ahead of 1.4.0 release #6033
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few changes, but very clear and easy to read :)
UPGRADE.rst
Outdated
In the medium term the vector.im and matrix.org Identity servers will disable | ||
sending email and SMS entirely, however in order to ease the transition they | ||
will retain the capability to send email and SMS for a limited period. Email | ||
will be disabled on XXX (giving 2 months notice), disabling SMS will follow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mental note: Make sure this gets filled in.
Co-Authored-By: Andrew Morgan <[email protected]>
Co-Authored-By: Andrew Morgan <[email protected]>
Co-Authored-By: Andrew Morgan <[email protected]>
Co-Authored-By: Andrew Morgan <[email protected]>
Co-Authored-By: Andrew Morgan <[email protected]>
Co-Authored-By: Andrew Morgan <[email protected]>
You can make batch updates from the Files tab btw |
Co-Authored-By: Andrew Morgan <[email protected]>
neil: please can you give the PR a better name? |
We're going to need to include the fact that adding threepids to your account won't work until the homeserver figures out how it's handling email/msisdns. This won't prevent you from binding threepids to Identity Servers through your homeserver at the protocol level, but Riot won't give you the option to bind until a threepid has been added to your account. |
Additionally, there are 4 more new email templates to worry about. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-
I have a few suggestions, but I think we're going to need to iterate on this.
-
What steps should I expect to have to take if I downgrade to v1.3.1? (particularly if I was foolish enough not to keep a copy of my old homeserver.yaml)
Co-Authored-By: Richard van der Hoff <[email protected]> Co-Authored-By: Andrew Morgan <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Plus some lines aren't correctly wrapped at 80 char (or whichever value we should use).
Co-Authored-By: Richard van der Hoff <[email protected]>
UPGRADE.rst
Outdated
In the medium term the vector.im and matrix.org identity servers will disable | ||
sending email and SMS for homeservers entirely, however in order to ease the | ||
transition they will retain the capability to send email and SMS for a limited | ||
period. Email will be disabled on Monday 2nd December 2019 (giving roughly 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this paragraph and the next still talk about stopping the ISes from sending email and sms altogether. I appreciate that you're trying to be brief for clarity but I worry that it's actively misleading - particularly given the repetition.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@richvdh I don't follow, is there some case where the IS sends an email on behalf of a homeserver that I am not thinking of? Or do I just need to make the fact I am talking about email and SMS on behalf of homeservers clearer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the latter. There are cases when an IS sends an email independently, so "Email will be disabled" is incorrect.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we should call it "support for delegated 3pid verification" or something, instead of "sending email"
Improve clarity Co-Authored-By: Richard van der Hoff <[email protected]>
…nto neilj/upgrade_notes
UPGRADE.rst
Outdated
|
||
It is possible for a user to associate an email address or phone number | ||
with their account, for a number of reasons: | ||
* for use when logging in, as an alternative to the user id. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there's a formatting fail here. I think it needs to lose the indentation
UPGRADE.rst
Outdated
matrix.org. | ||
|
||
In Synapse 1.4.0, for security and privacy reasons, the homeserver will no | ||
longer delegate 3pid validation to an identity server by default and instead the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably my bad, but we should decide if we are calling it 'verification' or 'validation'. I think 'verification'?
UPGRADE.rst
Outdated
In the medium term the vector.im and matrix.org identity servers will disable | ||
sending email and SMS for homeservers entirely, however in order to ease the | ||
transition they will retain the capability to send email and SMS for a limited | ||
period. Email will be disabled on Monday 2nd December 2019 (giving roughly 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we should call it "support for delegated 3pid verification" or something, instead of "sending email"
UPGRADE.rst
Outdated
Following upgrade, to continue sending email (and therefore register via an | ||
email address) admins can either:- | ||
|
||
* Configure Synapse to use an email server (details follow). * Run or choose an |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reflow formatting fail?
UPGRADE.rst
Outdated
Following upgrade, to continue sending email (and therefore register via an | ||
email address) admins can either:- | ||
|
||
* Configure Synapse to use an email server (details follow). * Run or choose an |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
formatting has broken here
UPGRADE.rst
Outdated
Delegate Email to an identity server | ||
------------------------------------ | ||
|
||
Some admins will wish to continue using email as a registration method, but |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's not a registration method
UPGRADE.rst
Outdated
will not immediately have an appropriate SMTP server to hand. | ||
|
||
To this end, we will continue to support email delegation via the vector.im and | ||
matrix.org identity servers for two months. The cut off date is Monday 2nd |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Support for delegated email verification will be disabled on Monday 2nd December.
UPGRADE.rst
Outdated
--- | ||
|
||
Following upgrade, the only way to maintain the ability to send SMS (and | ||
therefore register via a phone number) will be to continue to delegate SMS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/SMS delivery/phone number verification/
@@ -114,7 +226,8 @@ v1.3.1, subject to the following: | |||
The room statistics are essentially unused in v1.3.1 (in future versions of | |||
Synapse, they will be used to populate the room directory), so there should | |||
be no loss of functionality. However, the statistics engine will write errors | |||
to the logs, which can be avoided by setting the following in `homeserver.yaml`: | |||
to the logs, which can be avoided by setting the following in | |||
`homeserver.yaml`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👎
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see the problem, am wrapping to 80 chars.
UPGRADE.rst
Outdated
@@ -124,6 +237,7 @@ v1.3.1, subject to the following: | |||
Don't forget to re-enable it when you upgrade again, in preparation for its | |||
use in the room directory! | |||
|
|||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👎
server that supports SMS sending). | ||
|
||
|
||
The ``account_threepid_delegates`` dictionary defines whether the homeserver |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see comments above, though I'd love it if we could avoid repeating this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm just not sure I see a neat way not to repeat, since it is convenient to have the context close the description of what changes the admin must make. My sense is that since this is not a doc that needs maintenance the repetition is permissible, if you can see a better way to do it, just edit direct.
UPGRADE.rst
Outdated
<https://matrix.org/docs/spec/identity_service/r0.2.1>`_) to handle sending | ||
password reset or registration messages via email and SMS. | ||
|
||
So to delegate SMS sending set ``account_threepid_delegates.msisdn`` to a base |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
gtg, I think there are similar comments to be made below
Co-Authored-By: Andrew Morgan <[email protected]> Co-Authored-By: Richard van der Hoff <[email protected]>
…nto neilj/upgrade_notes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - SHIP IT!!!!!
Upgrade notes to explain changes in 1.4 brought about by privacy project
If you spot typos, things that are obviously wrong please just edit and commit direct.
Rendered