PEP 440 on fully autonomous forks versioning
"Sofia Nunes" <[email protected]>
| Newsgroups | gmane.comp.python.distutils.devel |
|---|---|
| Message-ID | <[email protected]> |
Hello, Regarding fork versioning, I found this thread: https://mail.python.org/archives/list/[email protected]/thread/XAAN4XMQ346TYIYG4BEM6AGDUXNQHMVX/#XAAN4XMQ346TYIYG4BEM6AGDUXNQHMVX Now, this is relating to forks that incorporate small changes, like bug fixes, and that are meant to be integrated upstream. When the fork implies greater changes, and is meant to be independent from the original package and have a different name, how should versioning work? From the following discussion, I get that probably the best method is to start as a fully independent distribution, for instance from version 1.0. https://bitbucket.org/pypa/pypi-metadata-formats/issues/1/add-local-numbering-to-pep-440 So, let’s assume I fork a package which is on version 2.1. and change its name. Would my distribution version be 1.0 or 2.2/3.0? Or none of the options? Thanks, Sofia Nunes -- Distutils-SIG mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/AWXLF6B6J7LCCYJ3KZK33EXSD2B3UYQW/