GitHub user tisonkun added a comment to the discussion: proposal: Release OpenDAL Components Seperately
> apache-opendal-binding-python-0.46.0+core.0.50.0 I don't like this version strategy. Either a binding should be compatible with a version range of core package, or we do releases simultaneously. Fixing the core version for a binding version increases the burden for downstream adopting, or if we do fix the core version, we omit the core version so that downstream users just pick against binding version. The point here is whether we make core package version associated to the bindings' version a public interface and how we define its semantic. GitHub link: https://github.com/apache/opendal/discussions/4126#discussioncomment-8355158 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
