version numbers

[daniel-baumann]

Hi,

thanks for pushing the 0.1.4 tag.

given that python-aristaproto is a fork of python-betterproto which was at version 1.2.5, it would be nice if python-aristaproto would use increased numbers on top of that, e.g. 1.4.0 instead of 0.1.4.

This would also ease continuation of python-aristaproto in debian, which I've intially uploaded versioned as 1.2+20240521 back in August 2024 (there are ways to workaround it with an epoche, but it would be cleaner and more future-proof if python-aristaproto had a higher version than 1.2).

Regards,
Daniel

[ClausHolbechArista]

I do not agree on this. aristaproto is a different project, and trying to fit versions depending on what we have cherry-picked will be very difficult. Also this is kept <1.0.0 on purpose.

[daniel-baumann]

aristaproto is a different project, and trying to fit versions [...] will be very difficult.

sure, and for the future you could use versioning completely at your own.

my input is:

• because python-aristaproto started off by forking python-betterproto at version 1.2 and
• because there were no tags ever pushed except last week, people that used it since >1 year in the wild (e.g. Debian, Ubuntu etc.) where using it as version 1.2

therefore python-aristaproto should have a version higher than 1.2, not lower.

[daniel-baumann]

jftr, we have '1.2+really0.1.4-1' in debian.

this means, until you reach a verson anything higher than 1.2, debian and all its derivative will have a debian-specific versionstring for python-aristaproto.

[ClausHolbechArista]

Thanks for the update. We will make sure to jump above 1.2 once we feel comfortable going >1.0.0. Thanks again.