Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: Explain Zulip Cloud branch in release lifecycle docs. 

Partial fix for #25482.
This commit is contained in:
Alex Vandiver 2023-05-15 18:46:06 +00:00 committed by Tim Abbott
parent 6cb570f3f0
commit 0117d751c2
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/overview/release-lifecycle.md
View File

@ -60,12 +60,12 @@ the Zulip server itself (E.g. `https://zulip.example.com/help/`).
Many Zulip servers run versions from Git that have not been published Many Zulip servers run versions from Git that have not been published
in a stable release. in a stable release.
- [Zulip Cloud](https://zulip.com) essentially runs the `main` - [Zulip Cloud](https://zulip.com) runs the `zulip-cloud-current`
branch. It is usually a few days behind `main` (with some branch; this the `main` branch, with some cherry-picked bug fixes,
cherry-picked bug fixes), but can fall up to 2 weeks behind when but delayed somewhat. It is usually one to two weeks behind `main`,
major UI or internals changes mean we'd like to bake changes longer depending on the complexity of recent major UI or internals changes
on chat.zulip.org before exposing them to the full Zulip Cloud that we'd like to bake longer on chat.zulip.org before exposing them
userbase. to the full Zulip Cloud userbase.
- [chat.zulip.org][chat-zulip-org], the bleeding-edge server for the - [chat.zulip.org][chat-zulip-org], the bleeding-edge server for the
Zulip development community, is upgraded to `main` several times Zulip development community, is upgraded to `main` several times
every week. We also often "test deploy" changes not yet in `main` every week. We also often "test deploy" changes not yet in `main`