liurenjie1024 commented on PR #212: URL: https://github.com/apache/iceberg-rust/pull/212#issuecomment-1954146668
> The difference lies in how we determine the version to release. > > Previously, we would decide on the version just before releasing it. This involved starting a discussion on the mailing list and then bumping up the version accordingly. However, now we must bump the version immediately without prior knowledge of what changes this release will include. For instance, should we release `0.3.0` even if there haven't been any breaking changes? I think in semver's semantics, upgrading different part has different meanings: 1. Upgrading major version means breaking change. For example, we can upgrade it to 1 when we have finished feature parity with java api, and upgrade it when we have breaking changes. 2. Upgrading minor version means add new features without breaking change, e.g. `0.2.0` -> `0.3.0`. Since we are currently adding features in main branch, so I think it's fine to upgrade minor version in main branch. 3. Upgrading patch version means adding bug fix without new feature, e.g. `0.2.0` -> `0.2.1`. In this case, we should create a 0.2.x branch for tags/0.2.0, and adding both bug fix pr to both main branch and 0.2.x, and create tags from 0.2.x branch for patch version. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
