Open MeggyCal opened 4 years ago
Here you go - https://github.com/vaidik/commentjson/releases/tag/v0.8.3. And sorry that I forgot to do this. I usually make releases.
Quick question, how do you use releases at your end? Just trying to understand to figure out the importance of making releases in my process.
Thanks a lot!
Well, I am a packager in SUSE and we are trying to test as many packages in the buildtime as possible. Since you (and many more Python developers, so I am aware) do not ship tests in PyPI tarball, we take Github tarball to have access to the tests.
Its not like we do not trust Travis results or so, launching the test is a kind of safety brake for us -- if a packager forgots some dependency (or the dependency is too old), the tests would fail. So we can be sure the packages with tests enabled are ready to be shipped in the distribution and that they won't break on the run. That's it.
Got it. I'll keep this issue open to make sure it is automated in someway so that I don't miss this again.
It seems v0.9.0 is missing again, I would like to wait for it before packaging for Arch. Thanks!
@felixonmars here you go - https://github.com/vaidik/commentjson/releases/tag/v0.9.0.
I'll make sure that I fix the release process before making another release.
Could you please tag all new releases in general and release 0.8.3 in particular on GitHub? Thanks!