Produce releases? about pywinrm HOT 17 CLOSED

Also, it would be good if the pip packages contained LICENSE and README.md for packaging.

from pywinrm.

@jmdh This is a defect in a README file. User should use pip install pywinrm==version instead of master. I will fix readme and will add release tags into the Git repository.

from pywinrm.

Great, thanks!

On Thu, Jun 11, 2015 at 04:51:04AM -0700, Alexey Diyan wrote:

@jmdh This is a defect in a README file. User should use pip install pywinrm==version instead of master. I will fix readme and will add release tags into the Git repository.

---

Reply to this email directly or view it on GitHub:
#57 (comment)

from pywinrm.

Hi Alexey, could you release a source tarball for the latest version? Debian is currently stuck at 0.1.1 (which is the latest source tarball released), and packaging directly from git repos is frowned upon. It would help to get the latest release of pywinrm into Debian before the release freeze.

from pywinrm.

@leegarrett actually 0.0.3, but thanks for spotting this. I have dropped the ball on keeping this package updated in Debian and agree it would be good to get this fixed for the freeze.

from pywinrm.

@leegarrett @jmdh OK, I will work on this. What do you need from my side other than tagging release on Github and updating CHANGELOG.md?

from pywinrm.

The release process isn't fully automated- I did the last couple with a bdist_wheel and didn't include an sdist. I think I might be able to add the sdist without doing a new release, but lemme try it on test-pypi first...

from pywinrm.

@diyan To make me fully happy, https://pypi.python.org/simple/pywinrm/ should have a pywinrm-0.2.1.tar.gz as an end result.

@jmdh I'm currently preparing a new release, and noticed that the usual steps would have me end up with 0.1.1.

from pywinrm.

@leegarrett I've added the corresponding sdist (.tar.gz) to the existing 0.2.1 release on pypi- does that get you where you need to be?

from pywinrm.

@nitzmahone I'm preparing 0.2.2 release. Do you have anything to add into CHANGELOG?

https://github.com/diyan/pywinrm/blob/master/CHANGELOG.md#version-022

from pywinrm.

@diyan Nope- the CredSSP stuff is the only thing that's been merged since 0.2.1, and Jordan already included it in the changelog in his PR. I was planning to do a pass over some Py3 bugs/tests to get everything happy before 0.2.2, but if you want to do it now, I can do that in 0.2.3 later...

from pywinrm.

@diyan Oh nevermind, you added it to the changelog just now. For the pypi deploy, are you set up to do both bdist_wheel and sdist? You only used to do sdists, so just want to make sure both are available.

from pywinrm.

@nitzmahone Let's tag 0.2.2 release now, ok?

In such way, @jmdh and @leegarrett could work on python2-winrm / python3-winrm packages for Debian. They have pretty outdated configuration and it will took some time to sync with latest pywinrm release.

Once you are ready you can tag bugfix release as v0.2.3 and guys will just increment version number.

from pywinrm.

For the pypi deploy, are you set up to do both bdist_wheel and sdist?

Shame on me but I have no idea how to setup this. Could you do this for me - tag releases on GitHub and PyPI? Everything is ready from what I see. Changelog is up-to-date all tests are green on Travis / AppVeyor

from pywinrm.

@diyan: No problem- that's why I asked. ;) I was able to add the tarball the Debian folks need to the existing 0.2.1 release on pypi. But I also think we're OK to release 0.2.2 now with just CredSSP support added. I know some folks are eagerly awaiting. :)

from pywinrm.

@nitzmahone Awesome. Please do it once you feel ready.

from pywinrm.

OK, 0.2.2 release is up on PyPI with CredSSP support- both sdist and bdist_wheel.

cc/ @jmdh @leegarrett - let me know if you need anything else on this end for packaging stuff. Thanks!

from pywinrm.