-
Notifications
You must be signed in to change notification settings - Fork 652
Improve version numbering for development releases #1083
Copy link
Copy link
Open
Labels
area/healthInvolves general matters of project configuration, health, maintenance, and similar concernsInvolves general matters of project configuration, health, maintenance, and similar concernsno QC knowledge neededDoes not require knowledge of quantum computingDoes not require knowledge of quantum computingpriority/after-0.7.7Leave to after the TFQ version 0.7.7 releaseLeave to after the TFQ version 0.7.7 release
Description
Metadata
Metadata
Assignees
Labels
area/healthInvolves general matters of project configuration, health, maintenance, and similar concernsInvolves general matters of project configuration, health, maintenance, and similar concernsno QC knowledge neededDoes not require knowledge of quantum computingDoes not require knowledge of quantum computingpriority/after-0.7.7Leave to after the TFQ version 0.7.7 releaseLeave to after the TFQ version 0.7.7 release
Type
Fields
Give feedbackNo fields configured for Task.
Multiple people have expressed confusion about the way version numbering is done in TensorFlow Quantum. In particular, the version in the main branch on GitHub is our active development version, but the form of the version number is not well-enough differentiated from the form of version numbers used in releases. For example, the current released version on PyPI is
0.7.6and the current version in main is0.7.7. Many other projects (including most of our other QAI projects) follow a practice of adding a suffix like.dev0to make it clear it is a development version. We should adopt a similar practice here.The Python packaging guide page on versioning provides some more examples and recommendations.