You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently each release of opentelemetry-python updates the version numbers for all the packages and release a new version. This is causing unnecessary churn for users, as new packages should really only be released when a change has been made.
I would like to propose that only packages that include changes be released when a release is done. This would require some changes to the maintainer release process and CI tooling. It would also mean that versioning, which has been in sync thus far, will start diverging.
Please vote on this discussion:
to keep versioning in sync and continue to release every package every time🚀
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently each release of opentelemetry-python updates the version numbers for all the packages and release a new version. This is causing unnecessary churn for users, as new packages should really only be released when a change has been made.
I would like to propose that only packages that include changes be released when a release is done. This would require some changes to the maintainer release process and CI tooling. It would also mean that versioning, which has been in sync thus far, will start diverging.
Please vote on this discussion:
Beta Was this translation helpful? Give feedback.
All reactions