Open johang opened 5 years ago
We've thought about it but haven't committed to any milestones or API stability within the subproject as things were rapidly changing in the past. It's something we could consider, but I think we need to fix up the build first. Manually running setup.py inside of our project for native tooling is probably not friendly to anyone packaging it.
They way I see it, it's two unrelated issues. You can do tags/releases now and then fix the setup.py issue at a later point in time. Also, you don't have commit to API stability, you just have to bump the version appropriately when you believe you break the API. You can break the API as many times you want as long as you bump the major version.
Have you guys considered creating tags and making releases of sdbusplus? Preferably something based on the principles of semantic versioning (https://semver.org/). That would make packaging and reuse of this library easier.