Deprecate TGI Gaudi fork in favor of the main TGI repo #287
+3
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… upstream of gaudi
baptistecolle
changed the title
|
@regisss You should also mark this repo as archived I think we can merge this PR when the latest PR in TGI is merged |
|
@baptistecolle @regisss Before marking this repo as archived, we need to finish the last 1.20 release this week. Thanks. |
|
Ok no problem, we can wait for that and then I can upstream the 1.20 release changes in the main TGI repo. Btw the release version will follow TGI. So release 1.20 will be v3.1.2 or something similar |
|
I think we can wait till the release of Synapse 1.21 before archiving this fork as the release aligned with Synapse 1.20 will be the last one in this repo and still be a valid one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR adds a notice to the README about the deprecation of this repository and informs users that future development should take place in the main TGI repository.
Context
We are currently in the process of upstreaming this fork into the main TGI repository. As a result, this repository is no longer needed, and all further Gaudi-related development will happen within TGI.
The TGI backend now provides equivalent functionality to tgi-gaudi, as it reuses the server from this repository.
Related PRs
• #3055: Introduces the Gaudi backend to TGI. For more details on TGI backends, see this blog post.
• #3091: Officially releases the Gaudi backend for TGI.
Next Steps
Three PRs from tgi-gaudi (#284, #285, and #286) have not yet been merged into the upstream Gaudi backend. I will submit a quick PR to add them to the new backend after the release.