lizhimins commented on issue #155: URL: https://github.com/apache/rocketmq-flink/issues/155#issuecomment-6594693711
Follow-up correcting the branch name in my previous comment, and settling the release-naming note. **The maintenance branch is [`v3.1.0`](https://github.com/apache/rocketmq-flink/tree/v3.1.0), not `v3.0`.** `v3.0.0` is already tagged (`04f20de`, 2026-09-22) against the pre-migration code, so the branch carrying the migrated code should not reuse that number. `v3.0` was created first and has been deleted; nothing was released from it and no PR targeted it. That also answers the GAV-collision note from my previous comment — the two lines now have distinct project versions, so **no Flink suffix is needed**: | branch | head | project version | `flink.version` | Java | | --- | --- | --- | --- | --- | | `main` | `ea50665` | **4.0.0** | 2.2.1 | 17 | | `v3.1.0` | `18fe9b8` | **3.1.0** | 1.20.3 | 11 | - #159 → `3.1.0` on `v3.1.0` - #160 → `4.0.0` on `main` Both merged, so the artifacts are `flink-sql-connector-rocketmq-3.1.0.jar` and `flink-sql-connector-rocketmq-4.0.0.jar`. Unlike `flink-connector-kafka`, which builds one version line against several Flink versions and therefore needs `3.4.0-1.18` / `-1.19` / `-1.20`, our two lines differ in version already, so the Flink segment would be redundant. All four steps of the proposal are now in place; fixes propagate by cherry-picking between `main` and `v3.1.0` (the diff between the two lines is exactly #158 plus the version bump). -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
