Provide stable Badger API

[rohanthewiz]

Is the API completely unstable? If not, then how about some tags to version lock to (semver.org).
Example git tag -a v0.1.1 -m "A usable release"

Thanks. I know it's a lot of work!

[manishrjain]

Sure, we should be able to do that. I think we can cut a v1.0 release of Badger soon, because we've been fortifying it for a while -- particularly with testing crash resilience against ALICE (blog post upcoming), we should be good.

Expect this in a few weeks.

[rohanthewiz]

Fantastic thanks!!

…

On Aug 14, 2017 2:18 AM, "Manish R Jain" ***@***.***> wrote: Sure, we should be able to do that. I think we can cut a v1.0 release of Badger soon, because we've been fortifying it for a while -- particularly with testing crash resilience against ALICE (blog post upcoming), we should be good. Expect this in a few weeks. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#161 (comment)>, or mute the thread <https:/notifications/unsubscribe-auth/ABE__9QKusdhQUON-iEb8IMtHxXpDYMiks5sX_SogaJpZM4O1-3N> .

[manishrjain]

Created a milestone for v1.0 -- aimed at end of this month -- though might be mid of next month.

[whyrusleeping]

Hey guys, any update here?

[manishrjain]

Hey @whyrusleeping, we've changed the APIs in a major way to introduce transactions to Badger (in develop branch). So, what we're going to do is to tag v0.8 as the current version of Dgraph, and when transactions land, they'd become master (and tagged as v0.9, this won't happen because of how gopkg.in works, we'll release txns directly as v1.0), leading up to v1.0.

This way, anyone on current APIs can continue to use them and switch whenever they're ready to.

[deepakjois]

We did a review of the API yesterday, and removed some methods which did not really belong in the public API, and were not being used externally.

What we have now is what will go into v1.0, which should be out soon pending a couple of minor bug fixes. But the API itself should not undergo any further changes. Closing this now.