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

Release 1.0.2 #79

Closed
dimon222 opened this issue Jan 13, 2020 · 2 comments · Fixed by #81
Closed

Release 1.0.2 #79

dimon222 opened this issue Jan 13, 2020 · 2 comments · Fixed by #81
Assignees

Comments

@dimon222
Copy link
Collaborator

We have done some patches for new python versions and for some JSON body endpoints.
I think it's safe to assume that's it's time to release new version of library after we merge #67

@kevin-bates
Copy link
Member

I agree. I'm also working on #63 and would like to include the PR for that when available. I'm having some difficulties with what appear to be multiple handlers getting involved, so just trying to work that out.

@kevin-bates
Copy link
Member

I'm wondering if we should get the repo moved first and the release can be relative to that new location - or might that be disruptive? I'm not that familiar with what all is involved in a move.

@lresende lresende self-assigned this Jan 14, 2020
@lresende lresende changed the title Time to release new version Release 1.0.2 Jan 14, 2020
@lresende lresende mentioned this issue Jan 14, 2020
lresende added a commit to lresende/hadoop-yarn-api-python-client that referenced this issue Jan 14, 2020
lresende added a commit to lresende/hadoop-yarn-api-python-client that referenced this issue Jan 22, 2020
lresende added a commit that referenced this issue Jan 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants