search

feast-dev / feast

The Open Source Feature Store for Machine Learning
https://feast.dev
Apache License 2.0
5.54k stars 993 forks source link

Create a release #65

Closed woop closed 5 years ago

woop commented 5 years ago

I think it's important that we separate any new development from bug fixes. We should have a release out of Feast that is stable and can be used in production.

If we want to develop new breaking changes then that should be prioritized for a future release, and development should maybe continue on a separate branch.

@tims @pradithya @zhilingc

tims commented 5 years ago

My preference is master represents the state of the art, and we have release branches if we want to backport fixes, they'd fork off from the release tag.

@woop is that what you had in mind?

woop commented 5 years ago

My preference is master represents the state of the art, and we have release branches if we want to backport fixes, they'd fork off from the release tag.

@woop is that what you had in mind?

Yes, that is the most logical. And we just continue with trunk based development on master.

tims commented 5 years ago

We discussed this in the community call I think, that we should make our first release 0.1.0. So we need to reset the version numbers in the pom and such.

tims commented 5 years ago

Let's discuss the strategy for making the release at next week's community call.

*I believe at this stage, we then just need to manually push a tag and then increment the dev version to 0.2.0-SNAPSHOT.

0.2.x can then include the api changes in #53

woop commented 5 years ago

Let's reopen this issue once we release 0.3.0