# Dgraph v2.0.0-rc1 release candidate
**URL:** https://discuss.dgraph.io/t/dgraph-v2-0-0-rc1-release-candidate/5988
**Category:** Announce
**Created:** [February 15, 2020, 2:01am UTC](https://discuss.dgraph.io/t/dgraph-v2-0-0-rc1-release-candidate/5988 "2020-02-15T02:01:08Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@dmai](https://discuss.dgraph.io/u/dmai)
#### Post date: [February 15, 2020, 2:01am UTC](https://discuss.dgraph.io/t/dgraph-v2-0-0-rc1-release-candidate/5988/1 "2020-02-15T02:01:08Z")
Hey folks,
Please try out our latest release candidate v2.0.0-rc1. If you find any issues, please let us know so we can address them before the final v2.0.0. See the [full list of changes](https://github.com/dgraph-io/dgraph/releases/tag/v2.0.0-rc1) on GitHub.
Link to binaries: [Linux](https://github.com/dgraph-io/dgraph/releases/download/v2.0.0-rc1/dgraph-linux-amd64.tar.gz), [Darwin](https://github.com/dgraph-io/dgraph/releases/download/v2.0.0-rc1/dgraph-darwin-amd64.tar.gz), [Windows](https://github.com/dgraph-io/dgraph/releases/download/v2.0.0-rc1/dgraph-windows-amd64.tar.gz).
Also published on [Docker tagged as v2.0.0-rc1](https://hub.docker.com/r/dgraph/dgraph/tags/).
**Note: This is not the official release.** You won’t be able to get these binaries using the [get.dgraph.io](http://get.dgraph.io/) quick install script.
Cheers,
The Dgraph Team
---
### Author:  [@marvin-hansen](https://discuss.dgraph.io/u/marvin-hansen)
#### Post date: [February 23, 2020, 11:57pm UTC](https://discuss.dgraph.io/t/dgraph-v2-0-0-rc1-release-candidate/5988/2 "2020-02-23T23:57:40Z")
@dmai
Three questions:
1. Is there _any_ hope for a policy to keep the data format constant within one version number so we can update just the container without the permanent data export-import?
I understand this is a pre-release, and things may break or change at any time, but my real question is whether you even consider keeping the format stable for all 2.x versions? It’s really frustrating to constantly export/import especially when I can’t do a round-robin patching of a running cluster.
2. Has the new GraphQL endpoint actually been tested on an HA cluster?
When I did my testing on a single node, everything worked exactly as supposed, but since I am working on a 5 node cluster, I am facing an endless series of totally strange issues, several of them [already reported](https://github.com/dgraph-io/dgraph/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+GraphQL+).
3. Is there a rough estimate when the final version arrives?
Thank you
---
### Author:  [@dmai](https://discuss.dgraph.io/u/dmai)
#### Post date: [April 16, 2020, 3:57pm UTC](https://discuss.dgraph.io/t/dgraph-v2-0-0-rc1-release-candidate/5988/3 "2020-04-16T15:57:48Z")
> [@marvin-hansen](#):
>
> Is there _any_ hope for a policy to keep the data format constant within one version number so we can update just the container without the permanent data export-import?
With Dgraph [adopting calendar versioning](https://dgraph.io/blog/post/dgraph-calendar-versioning/) starting in v20.03.0, any patch releases for that release series will not contain any breaking changes.
> [@marvin-hansen](#):
>
> Has the new GraphQL endpoint actually been tested on an HA cluster?
These should be addressed in the latest v20.03.0 release which was released in March.