2019-04-21 05:51:20 +02:00
|
|
|
import os
|
|
|
|
|
2019-12-13 07:53:52 +01:00
|
|
|
ZULIP_VERSION = "2.2.dev+git"
|
2019-04-21 05:51:20 +02:00
|
|
|
# Add information on number of commits and commit hash to version, if available
|
|
|
|
zulip_git_version_file = os.path.join(os.path.dirname(os.path.abspath(__file__)), 'zulip-git-version')
|
|
|
|
if os.path.exists(zulip_git_version_file):
|
|
|
|
with open(zulip_git_version_file) as f:
|
|
|
|
version = f.read().strip()
|
|
|
|
if version:
|
|
|
|
ZULIP_VERSION = version
|
|
|
|
|
2019-12-13 06:13:31 +01:00
|
|
|
LATEST_MAJOR_VERSION = "2.1"
|
2020-04-16 23:16:47 +02:00
|
|
|
LATEST_RELEASE_VERSION = "2.1.4"
|
2019-12-13 06:13:31 +01:00
|
|
|
LATEST_RELEASE_ANNOUNCEMENT = "https://blog.zulip.org/2019/12/13/zulip-2-1-released/"
|
2020-04-02 07:59:30 +02:00
|
|
|
LATEST_DESKTOP_VERSION = "5.0.0"
|
2017-11-16 21:40:36 +01:00
|
|
|
|
2020-04-01 22:11:26 +02:00
|
|
|
# Versions of the desktop app below DESKTOP_MINIMUM_VERSION will be
|
|
|
|
# prevented from connecting to the Zulip server. Versions above
|
|
|
|
# DESKTOP_MINIMUM_VERSION but below DESKTOP_WARNING_VERSION will have
|
|
|
|
# a banner at the top of the page asking the user to upgrade.
|
|
|
|
DESKTOP_MINIMUM_VERSION = "5.0.0"
|
|
|
|
DESKTOP_WARNING_VERSION = "5.0.0"
|
|
|
|
|
2020-04-20 00:57:28 +02:00
|
|
|
# Bump the API_FEATURE_LEVEL whenever an API change is made
|
|
|
|
# that clients might want to condition on. If we forget at
|
|
|
|
# the time we make the change, then bump it later as soon
|
|
|
|
# as we notice; clients using API_FEATURE_LEVEL will just not
|
|
|
|
# use the new feature/API until the bump.
|
|
|
|
#
|
|
|
|
# Changes should be accompanied by documentation explaining what the new
|
|
|
|
# level means in templates/zerver/api/server-settings.md.
|
|
|
|
API_FEATURE_LEVEL = 1
|
|
|
|
|
2017-12-26 07:57:39 +01:00
|
|
|
# Bump the minor PROVISION_VERSION to indicate that folks should provision
|
|
|
|
# only when going from an old version of the code to a newer version. Bump
|
|
|
|
# the major version to indicate that folks should provision in both
|
|
|
|
# directions.
|
|
|
|
|
2019-07-22 04:00:19 +02:00
|
|
|
# Typically,
|
|
|
|
# * adding a dependency only requires a minor version bump;
|
|
|
|
# * removing a dependency requires a major version bump;
|
|
|
|
# * upgrading a dependency requires a major version bump, unless the
|
|
|
|
# upgraded dependency is backwards compatible with all of our
|
|
|
|
# historical commits sharing the same major version, in which case a
|
|
|
|
# minor version bump suffices.
|
2017-12-26 07:57:39 +01:00
|
|
|
|
db tools: Use common scheme for digests.
We have two different digest schemes to make
sure we keep the database up to date. There
is the migration digest, which is NOT in the
scope of this commit, and which already
used the mechanism we use for other tools.
Here we are talking about the digest for
important files like `populate_db.py`.
Now our scheme is more consistent with how we
check file changes for other tools (as
well as the aformentioned migration files).
And we only write one hash file, instead of
seven.
And we only write the file when things have
actually changed.
And we are explicit about side effects.
Finally, we include a couple new bot settings
in the digest:
INTERNAL_BOTS
DISABLED_REALM_INTERNAL_BOTS
NOTE: This will require a one-time transition,
where we rebuild both databases (dev/test).
It takes a little over two minutes for me,
so it's not super painful.
I bump the provision version here, even
though you don't technically need it (since
the relevant tools are actually using the
digest files to determine if they need to
rebuild the database). I figure it's just
good to explicitly make this commit trigger
a provision, and the user will then see
the one-time migration of the hash files
with a little bit less of a surprise.
And I do a major bump, not a minor bump,
because when we go in the reverse direction,
the old code will have to rebuild the
database due to the legacy hash files not
being around, so, again, I just prefer it
to be explicit.
2020-04-22 11:47:03 +02:00
|
|
|
PROVISION_VERSION = '80.0'
|