# Dgraph v1.0.7 release

**URL:** <https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005>\
**Category:** Announce\
**Created:** [August 10, 2018, 9:50pm UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005 "2018-08-10T21:50:34Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrjn](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/mrjn/32/775_2.png) [@mrjn](https://discuss.dgraph.io/u/mrjn)\
**Post date:** [August 10, 2018, 9:50pm UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/1 "2018-08-10T21:50:35Z")

</div>

Hey all,

First of all, thanks for your support. Dgraph has gone beyond 6000 Github stars, in just over 2.5 years, it’s incredible! It is now being used in production by big-name companies, which makes us proud and anxious at the same time. So, thanks for all your love and feedback.

We’re glad to announce v1.0.7 release of Dgraph.

> **[Release Dgraph v1.0.7 · dgraph-io/dgraph](https://github.com/dgraph-io/dgraph/releases/tag/v1.0.7)**
>
> Improvements:
> 
> All Oracle delta streams are applied via Raft proposals. This deals better with network partition like edge-cases.
> Fix deadlock in 10-node cluster convergence (eb3910c).
> Make ReadInd...

Docker tags: v1.0.7, latest

It contains a lot of bug fixes since v1.0.6 and makes the system run a lot smoother compared to earlier versions. More information in the release notes.

You can get it with `curl https://get.dgraph.io -sSf | bash`.

Let us know your experiences with this version. Looking forward to your hearing about your experiences with this version.

Keep building!  
-Manish and the Dgraph team

---

<div class="post-metadata">

**Author:** ![mrjn](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/mrjn/32/775_2.png) [@mrjn](https://discuss.dgraph.io/u/mrjn)\
**Post date:** [August 10, 2018, 9:50pm UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/2 "2018-08-10T21:50:45Z")

</div>



---

<div class="post-metadata">

**Author:** ![ian19861](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/ian19861/32/984_2.png) [@ian19861](https://discuss.dgraph.io/u/ian19861)\
**Post date:** [August 14, 2018, 6:36am UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/3 "2018-08-14T06:36:53Z")

</div>

Can you publish list big-name companies

---

<div class="post-metadata">

**Author:** ![mrjn](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/mrjn/32/775_2.png) [@mrjn](https://discuss.dgraph.io/u/mrjn)\
**Post date:** [August 14, 2018, 12:24pm UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/4 "2018-08-14T12:24:09Z")

</div>

Not yet, would require permissions etc. But, can say that at least one of them is in Global Fortune 500 list.

---

<div class="post-metadata">

**Author:** ![ian19861](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/ian19861/32/984_2.png) [@ian19861](https://discuss.dgraph.io/u/ian19861)\
**Post date:** [August 14, 2018, 3:45pm UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/5 "2018-08-14T15:45:57Z")

</div>

1. How many big-name companies using dgraph
2. possible to get testimony ?
3. How many not given permission to tell name  
neo4j published, [Neo4j Customers - Neo4j Graph Database Platform](https://neo4j.com/customers/). Dgraph doesn’t want to publish or companies give no permission to publish ?

Jepsen why no publish test results yet ? Started testing in March

---

<div class="post-metadata">

**Author:** ![shanea](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/shanea/32/968_2.png) [@shanea](https://discuss.dgraph.io/u/shanea)\
**Post date:** [August 14, 2018, 3:56pm UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/6 "2018-08-14T15:56:56Z")

</div>

Hi Ian19861

Is there something be can help you achieve? Could we know what you are hoping to use this info for? If so, maybe we can provide an alternative solution to help you achieve your goals?

---

<div class="post-metadata">

**Author:** ![ian19861](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/ian19861/32/984_2.png) [@ian19861](https://discuss.dgraph.io/u/ian19861)\
**Post date:** [August 14, 2018, 4:30pm UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/7 "2018-08-14T16:30:47Z")

</div>

You mentioned big companies using, so wanted to know names.  
If don’t want to tell or they give no permission or don’t want to ask permission, then don’t tell

Seeing too many issues closed in github since production ready release. Some critical issues.  
What does production ready means ? Want to know from others how they using dgraph. Amount of data they put in graph, issues they faced. Which version they using in production.

So much work going on stability and bug fixes after production ready dgraph release without any features. Why so many fixes. Is it performance improvements ? i see no significant difference. Stability fixes ? Continous fixes(bug or stability) 7 month after release and no features not give me confidence.

To confidence stability in dgraph, want 3rd party results. Saw in github that jepsen started test so want to know result from him.

Don’t want to tell then don’t tell.

---

<div class="post-metadata">

**Author:** ![ethanlynn](https://avatars.discourse-cdn.com/v4/letter/e/53a042/32.png) [@ethanlynn](https://discuss.dgraph.io/u/ethanlynn)\
**Post date:** [August 16, 2018, 4:12pm UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/8 "2018-08-16T16:12:53Z")

</div>

Still waiting for user authentication and gremlin support 🙂

---

<div class="post-metadata">

**Author:** ![enzotar](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@enzotar](https://discuss.dgraph.io/u/enzotar)\
**Post date:** [August 18, 2018, 8:55pm UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/9 "2018-08-18T20:55:51Z")

</div>

I agree with @ian19861

It would give confidence, and reduce the hesitation to start a project with Dgraph, if we knew who else is using it in production and more details about their use-case/progress/etc. I would ask permission from every company that is using Dgraph in production and feature it on the site.

And to contribute to @ethanlynn point, I think a production release should have authentication.

---

<div class="post-metadata">

**Author:** ![shanea](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/shanea/32/968_2.png) [@shanea](https://discuss.dgraph.io/u/shanea)\
**Post date:** [August 18, 2018, 10:59pm UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/10 "2018-08-18T22:59:02Z")

</div>

Understood. We are doing the arduous work to release the companies we work with. So in the meantime, I encourage you to do something small with dgraph and let it speak for itself. We’re here to help.

> [@enzotar](#):
>
> And to contribute to @ethanlynn point, I think a production release should have authentication.

–ack

---

<div class="post-metadata">

**Author:** ![enzotar](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@enzotar](https://discuss.dgraph.io/u/enzotar)\
**Post date:** [August 23, 2018, 5:02pm UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/11 "2018-08-23T17:02:38Z")

</div>

[https://jepsen.io/analyses/dgraph-1-0-2](https://jepsen.io/analyses/dgraph-1-0-2)

---

<div class="post-metadata">

**Author:** ![emhagman](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/emhagman/32/1191_2.png) [@emhagman](https://discuss.dgraph.io/u/emhagman)\
**Post date:** [August 28, 2018, 1:51am UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/12 "2018-08-28T01:51:21Z")

</div>

What is in the v1.0.7a release? I saw the image on Docker and the tag on Github but see no explanation of it.

---

<div class="post-metadata">

**Author:** ![mrjn](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/mrjn/32/775_2.png) [@mrjn](https://discuss.dgraph.io/u/mrjn)\
**Post date:** [August 28, 2018, 6:33pm UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/13 "2018-08-28T18:33:23Z")

</div>

Has a little HTTP endpoint in Zero to allow allocating IDs.

> <https://github.com/dgraph-io/dgraph/commit/fa4741138672e0a54740aceef0cd2aa68ed4d0ac>

---

<div class="post-metadata">

**Author:** ![BlankRain](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/blankrain/32/1592_2.png) [@BlankRain](https://discuss.dgraph.io/u/BlankRain)\
**Post date:** [August 30, 2018, 9:36am UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/14 "2018-08-30T09:36:55Z")

</div>

哈哈哈, 怕了你了…  
尤其最后一句… 中式英语很拉风～

---

<div class="post-metadata">

**Author:** ![BlankRain](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/blankrain/32/1592_2.png) [@BlankRain](https://discuss.dgraph.io/u/BlankRain)\
**Post date:** [August 30, 2018, 9:38am UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/15 "2018-08-30T09:38:25Z")

</div>

you can do user authentication in your APP level instead of waiting.

---

<div class="post-metadata">

**Author:** ![mrjn](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/mrjn/32/775_2.png) [@mrjn](https://discuss.dgraph.io/u/mrjn)\
**Post date:** [August 31, 2018, 9:36pm UTC](https://discuss.dgraph.io/t/dgraph-v1-0-7-release/3005/16 "2018-08-31T21:36:34Z")

</div>


