Because we are planning to start publishing SNAPSHOTS of GraphFrames, it will be possible to follow a better release process.

Due to limited resources (especially a lack of managers), I don’t think we’ll be able to follow the “ideal” process with a dedicated release manager, release candidates, voting, and so on. However, what I can do is declare a freeze before each release, open a “release PR” that bumps the version, and notify all dependent projects about the planned release. These projects can then test the latest SNAPSHOT of GraphFrames, and the responsible persons from each project can approve the PR or leave comments about any potential issues or bugs. After collecting all approvals (or after a reasonable deadline), I’ll merge the PR along with any discussed fixes and publish a new release.

This approach will require maintaining a list in the format “project” → “responsible person’s GitHub account.”

Thoughts?