Skip to content
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

pysipp release #42

Open
y-luis-rojo opened this issue Aug 21, 2018 · 12 comments
Open

pysipp release #42

y-luis-rojo opened this issue Aug 21, 2018 · 12 comments

Comments

@y-luis-rojo
Copy link
Contributor

Is there any plan to make a pysipp release in a short time?

@goodboy
Copy link
Member

goodboy commented Aug 21, 2018

@y-luis I think this is a good idea.
I'm not actively working on this project any more but if we can wrap up the PRs you've brought in I think we might as well push a 0.1.0 to pypi.

@goodboy goodboy self-assigned this Aug 21, 2018
@goodboy
Copy link
Member

goodboy commented Aug 23, 2018

@y-luis @vodik @wdoekes so just to clear up the rumours.

My plan is

  • push a first version to pypi that will be the last version which supports python 2.7
    • we'll need to document this of course
    • Question: is it cool to be pushing a python package that requires an external program to be installed? Right now I believe an error will be raised on import or at the least at runtime.
  • port the process launching code to selectors which should give us cross-platform support for free (i.e. as per Support for OS X #16 and Can't import pysipp after install #34)

Anyone who wants to help with that last bit is greatly welcomed!

@luismartingil
Copy link

@goodboy Any news on getting a release done? At least an alpha version for pypi with the current state of master branch?

@goodboy
Copy link
Member

goodboy commented May 22, 2019

Hey @luismartingil yes this definitely needs to get done.
Sticking on my sticky note list!

I'll see what I can do this week.

@goodboy
Copy link
Member

goodboy commented May 24, 2019

It'd be nice to see #46 land before this.

@goodboy
Copy link
Member

goodboy commented May 27, 2019

@luismartingil @y-luis As I'm sure it's clear I haven't been maintaining this project very well for some time as I'm not using it for any project work currently. Is there any interest in helping on that front?

It would be good to have some contributors who are using the project to possibly help with a release process and CI maintenance at the least.

@y-luis-rojo
Copy link
Contributor Author

@goodboy, currently I am not working on any related project and I am afraid I will not have enough time for the time being, but thanks for asking.

@luismartingil
Copy link

@goodboy I believe we can start taking the lead here. Any suggestions on how to proceed? Thanks

@goodboy
Copy link
Member

goodboy commented Jun 10, 2019

@luismartingil first thing is getting the outstanding blocker issues complete to get a first alpha release out.

Right now this includes:

  • testing to get pypy working manually and then in travis
  • closing out the remaining bug issues via PRs and testing

Again sorry it turns out I won't have time to look at this until at least beginning of next month.

This was referenced Jul 4, 2019
@goodboy
Copy link
Member

goodboy commented Jul 4, 2019

Do we care about OS X support for this release team?

I'm thinking let's get something up and move onto dropping py2.7!

@goodboy
Copy link
Member

goodboy commented Jul 5, 2019

@y-luis @luismartingil check #54 for the release candidate branch!

@linuxmaniac
Copy link
Contributor

@goodboy I am willing to help here since I'm planning to use the project for several customers. I'm the Debian maintainer of sipp already and I would love to help keeping the project alive

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants