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

Migrate from 'Stream' to 'Channel' naming #1510

Open
8 tasks
neiljp opened this issue Jun 2, 2024 · 0 comments
Open
8 tasks

Migrate from 'Stream' to 'Channel' naming #1510

neiljp opened this issue Jun 2, 2024 · 0 comments
Labels
area: documentation Requires changes in documentation area: UI General user interface update high priority should be done as soon as possible TRACKING version parity: 9
Milestone

Comments

@neiljp
Copy link
Collaborator

neiljp commented Jun 2, 2024

Client terminology migration description

Like other migrations of this type, this should eventually include updating:

  • User-visible UI
  • Documentation
  • Any API usage
  • Terminology internal to the application

In terms of priority, the first two areas are the most important, followed by the API and internal terminology. The latter areas may be small (easy to do with the initial work) or large (which could be broken into separate issues later).

The substitution in each case should be fairly straightforward, however for this migration it is important to

  • confirm at which Zulip feature level the Server (web app) made this change (see the API changelog)
  • ensure the UI shows the appropriate term based on the server (zulip) feature level (ZFL in our source), so using an older server will look similar to the web app and mobile
  • update the documentation to 'Channel', but possibly add a FAQ entry for the renaming? (eg. mismatch between UI & docs?
  • only use any updated API language after the associated feature level at which they were introduced (which may be different to the UI change ZFL)

Resources for this migration:

@neiljp neiljp added area: UI General user interface update area: documentation Requires changes in documentation TRACKING labels Jun 2, 2024
@neiljp neiljp added this to the Next Release milestone Jun 2, 2024
@neiljp neiljp added version parity: 9 high priority should be done as soon as possible labels Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: documentation Requires changes in documentation area: UI General user interface update high priority should be done as soon as possible TRACKING version parity: 9
Projects
None yet
Development

No branches or pull requests

1 participant