Skip to content

chore: Update docs with new release workflow #2898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kevjumba merged 14 commits into from
Jul 12, 2022
Merged

chore: Update docs with new release workflow #2898

Changes from 1 commit
Commits
Show all changes
14 commits
Select commit Hold shift + click to select a range
ecf99f0
Update docs
kevjumba Jun 30, 2022
54d9fbe
Fix
kevjumba Jun 30, 2022
00651be
Fix
kevjumba Jun 30, 2022
748213b
Fix
kevjumba Jun 30, 2022
136258d
Fix
kevjumba Jul 1, 2022
b779e51
Fix
kevjumba Jul 1, 2022
1820ae9
Fix
kevjumba Jul 1, 2022
cdb5005
Fix
kevjumba Jul 1, 2022
4f1c410
Fix
kevjumba Jul 1, 2022
ae4bc72
Fix
kevjumba Jul 1, 2022
256bc63
Fix
kevjumba Jul 1, 2022
a8ca125
Fix
kevjumba Jul 1, 2022
8bc5b1c
Fix
kevjumba Jul 1, 2022
bb2e4c7
Fix
kevjumba Jul 5, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fix 
Signed-off-by: Kevin Zhang <kzhang@tecton.ai>
  • Loading branch information
@kevjumba
kevjumba committed Jul 1, 2022
commit 1820ae968a25338a40fc83d9ff6c7f05579c1600
6 changes: 0 additions & 6 deletions docs/project/release-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,3 @@ For Feast maintainers, these are the concrete steps for making a new release.
4. Try the dry run first with your personal access token. If this succeeds, uncheck `Dry Run` and run the release workflow.
5. All of the jobs should succeed besides the UI job which needs to be released separately. Ping a maintainer on Slack to run the UI release manually.
6. Try to install the feast release in your local environment and test out the `feast init` -> `feast apply` workflow to verify as a sanity check that the release worked correctly.

### Flag Breaking Changes & Deprecations

It's important to flag breaking changes and deprecation to the API for each release so that we can maintain API compatibility.

Developers should have flagged PRs with breaking changes with the `compat/breaking` label. However, it's important to double check each PR's release notes and contents for changes that will break API compatibility and manually label `compat/breaking` to PRs with undeclared breaking changes.