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.

Sign up for GitHub

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

Jump to bottom

Release 1.1.0 🎉 #57

Open
wants to merge 27 commits into
base: master
Choose a base branch
from
Open

Release 1.1.0 🎉 #57

wants to merge 27 commits into from

Conversation

lbeckman314
Copy link
Member

Includes all updates made to the release-1.1.0 branch, including support for TES v1.1

uniqueg and others added 10 commits February 9, 2023 23:43
@uniqueg
feat: support Python 3.7+; drop Python 2.7,<3.7
2d23493
@uniqueg
feat: pass through json serialization options
c30424c
@uniqueg
docs: add advanced usage examples
1abde51
@kellrott
Merge pull request #44 from uniqueg/upgrade-python
a90cd3e 
Towards v0.5.0
@uniqueg
feat: spec-compliant routes, with legacy support
3ac3052
@kellrott
Merge pull request #46 from ohsu-comp-bio/api-location
5379b2a 
feat: spec-compliant suffixes, with legacy support
@uniqueg @lbeckman314
fix: remove debug messages
e67ab6e
@uniqueg @lbeckman314
test: increase unit test coverage (#52)
93ad675 
* test: increase unit test coverage

* Update tests.yml

---------

Co-authored-by: Liam Beckman <[email protected]>
@uniqueg @lbeckman314
docs: browsable API reference on GitHub Pages (#49)
a0683d8 
* docs: browsable API reference on GitHub Pages

* Update tests.yml

---------

Co-authored-by: Liam Beckman <[email protected]>
@lbeckman314
Minor release testing updates
7913526
@lbeckman314 lbeckman314 mentioned this pull request Jan 18, 2024
Closed
@lbeckman314 lbeckman314 self-assigned this Jan 18, 2024
@uniqueg
Copy link
Collaborator

uniqueg commented Jan 22, 2024 •
edited
Loading

Awesome, Liam 🚀

I'm curious (but too lazy/busy to dive into the code): Is py-tes 1.1.0 backwards-compatible with TES 1.0.0 servers? And is there are general policy how client/server compatibility will be handled for py-tes (e.g. extra code, different branches, only maintaining support for latest server version)? Might be good to include some info on this in the docs.

@github-pages github-pages bot temporarily deployed to github-pages February 1, 2024 22:41 Inactive
@lbeckman314
Update support for Service Info (#55)
4d12b82 
- Fix version to match PyPi release (#59)
@lbeckman314
Copy link
Member Author

lbeckman314 commented Feb 29, 2024 •
edited
Loading

Hi Alex! Apologies for the astronomically late reply — backwards-compatibility with TES 1.1.0 servers is definitely something that we should ensure prior to this release, with steps for handling different versions being added to the documentation like you recommend.

Whether that support is from extra code or handled different branches is still a question to be answered.

Having the version support be on different branches is perhaps the quickest/easiest way in the short term, with maybe a long-term goal of having this be configurable both on the command line and within the tes module (manually by the user or automatically by querying the server).

I've just created a new issue for this (#60) to track the progress on this. Please add any thoughts or suggestions on this compatibility support and we'll go from there! 🚀

@vsmalladi
Copy link

@lbeckman314 is this released yet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@lbeckman314 lbeckman314

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@lbeckman314 @uniqueg @vsmalladi @kellrott @musicinmybrain