Skip to content
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

Prepare v0.2.0 release #87

Merged
merged 1 commit into from
Dec 17, 2024
Merged

Prepare v0.2.0 release #87

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
16 changes: 16 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,3 +107,19 @@ are started. You can also see the required environment variables from

We use `cargo-fmt` as formatter and `cargo-clippy` as linter. You can check
how we run them from [ci.yml](.github/workflows/ci.yml).


# Release

We apply semantic versioning for our releases. We do not support long term release branches (backporting) yet.
The release process is as follows:

1. Open PR to start release preparation,
2. Bump the package version at `Cargo.toml` file
3. Upgrade dependencies via `cargo update`
4. Use a schema diff tool, if possible (or manually), to generate
- sql upgrade file from previous release to the current release `pg_parquet--<prev-version>-<next-version>.sql`
- sql file of the current schema `pg_parquet.sql`
5. Merge the PR into main
6. Tag the latest commit with naming convention of `v<major>.<minor>.<patch>`
7. Release it with important and breaking (if any) changes
Loading
Loading