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.

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

Document planned release cadence for arrow/parquet/etc #5737

Merged
merged 6 commits into from
May 11, 2024

Conversation

alamb
Copy link
Contributor

@alamb alamb commented May 9, 2024

Which issue does this PR close?

Related to #5368

Rationale for this change

We spent a while discussing release cadence in #5368 so let's document that clearly on in the readmes

What changes are included in this PR?

Document the planed release cadence.

Add links in parquet / arrow-rs readme

Are there any user-facing changes?

Documentation, no functional changes

@alamb alamb added the development-process Related to development process of arrow-rs label May 9, 2024
@github-actions github-actions bot added parquet Changes to the parquet crate arrow Changes to the arrow crate labels May 9, 2024
`arrow-flight`, etc.) are released on the same schedule with the same versions
as the `parquet` and `parquet-derive` crates.

Starting June 2024, we plan to release new major versions with potentially
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this accurately summarizes the plan from #5368

README.md Outdated Show resolved Hide resolved
@Xuanwo
Copy link
Member

Xuanwo commented May 9, 2024

Do we have a plan to object_store? I'm guessing a breaking change to object_store could also affect parquet?

@tustvold
Copy link
Contributor

tustvold commented May 9, 2024

Do we have a plan to object_store? I'm guessing a breaking change to object_store could also affect parquet?

Nothing formal, but a natural implication of this would be that if we made a breaking release to object_store we would be unable to incorporate this into arrow until the next arrow breaking release. In practice this means object_store will likely follow a similar cadence for breaking releases, if not slower. It has a much smaller API surface and so it should be easier to avoid making breaking changes.

README.md Outdated Show resolved Hide resolved
Co-authored-by: Raphael Taylor-Davies <1781103+tustvold@users.noreply.github.com>
@alamb
Copy link
Contributor Author

alamb commented May 10, 2024

I plan to add a note about object_store release schedules, likely as a follow on PR

@alamb alamb merged commit 68ecc16 into apache:master May 11, 2024
23 of 24 checks passed
@alamb
Copy link
Contributor Author

alamb commented May 11, 2024

I am working on a follow up PR for object_store cadence

Update: #5750

@alamb alamb deleted the alamb/release_cadence branch May 11, 2024 10:03
README.md Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arrow Changes to the arrow crate development-process Related to development process of arrow-rs parquet Changes to the parquet crate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants