BewareMyPower commented on PR #3: URL: https://github.com/apache/pulsar-client-python/pull/3#issuecomment-1263096492
> We now have the freedom of doing releases with much less overhead and we can release new features much quicker than before. I'm wondering how to manage the releases for C++ client now. If the main branch must depend on a released C++ client, then, if we want to support a new feature, we have to release the C++ client first. Then **each C++ feature requires a release**. I'm afraid that it's not a good way for release even if the release could be much quicker than before. We might have: - pulsar-cpp-3.0.0-pre-feature1 - pulsar-cpp-3.0.0-pre-feature2 - pulsar-cpp-3.0.0-pre-feature3 - ... Adding a git tag for them might be good (but I think it could still create a lot of tags). But should we create each binary uploaded for **a single feature**? @merlimat -- 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]
