-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: please start making github releases #3296
Comments
Copying my comment from f41d78d#commitcomment-113899124 Our distribution mechanism is PyPI, not github releases, and this will always remain the authoritative source as the standard for the python ecosystem. I do not want to set up another non-authoritative distribution system just to support different notification workflows. I recommend you use one of the services that can send notifications based on updates to PyPI packages. |
This RFE is not about release by any meaning. |
But unfortunately github releases do create a new distribution channel. Each github release shows a download link for a source tarball that is just a copy of the git repo contents. This looks like a python source distribution but is different from the If github had a release announcement system that was really just about notifications, then I might be willing to use it, but I still don't think it's a great idea because not all python projects are on github (and those that are might want to preserve the option to move away). All python projects are, however, on pypi so pypi-based notifications will always be the most complete and robust. |
Again: this RFE has nothing to do with any files, tar balls, chanels or so. |
Is it possible next time on release new version make the github release to have entry on https://github.com/tornadoweb/tornado/releases? 🤔
I'm asking because only on make gh release is spread notification about new release to those who have set watch->releases.
The text was updated successfully, but these errors were encountered: