Closed brifordwylie closed 9 years ago
I guess what I asked in #10 should actually be discussed here.
Is this a good moment in time to perhaps define a release procedure?
It doesn't have to be anything particularly fancy, but just specifying some basic criteria by which we say the code is in good quality to make a new release and what are the steps required to cut it (tag the git repo with a certain semantic, push a gpg signed tarbal to pypi, etc.).
Arturo,
If you want I'll add a setup.cfg script that allows us to just do a $python setup.py release with a gpg signature...
-bri
On Mon, Sep 7, 2015 at 12:12 PM, Arturo Filastò notifications@github.com wrote:
I guess what I asked in #10 https://github.com/pynetwork/pypcap/pull/10 should actually be discussed here.
Is this a good moment in time to perhaps define a release procedure? It doesn't have to be anything particularly fancy, but just specifying some basic criteria by which we say the code is in good quality to make a new release and what are the steps required to cut it (tag the git repo with a certain semantic, push a gpg signed tarbal to pypi, etc.).
— Reply to this email directly or view it on GitHub https://github.com/pynetwork/pypcap/issues/9#issuecomment-138351291.
That would be great. Go for it!
Greeting and Salutations,
The current PyPI release of pypcap basically doesn't work for network interfaces on many Macs without PR #8. I'd love to do another pypi release with the fix in it.