Vaibhavs10/open-tts-tracker
1
0
Fork 0
Code Issues 6 Pull requests 2 Projects Releases Packages Wiki Activity Actions

Add release dates #27

Open
Ryu1845 wants to merge 3 commits from Ryu1845/release-order into main
pull from: Ryu1845/release-order
merge into: Vaibhavs10:main
Conversation 7 Commits 3 Files changed 1 +30 -30
Ryu1845 commented 2024-02-07 16:01:34 -05:00 (Migrated from github.com)
Copy link

Add latest release dates and sort by newest as proposed in #9 .

Since many of the projects on the tracker don't have formal incremental releases, I use the date of the latest user visible feature addition. This is pretty fuzzy, so I'm open to other proposals.

Add latest release dates and sort by newest as proposed in #9 . Since many of the projects on the tracker don't have formal incremental releases, I use the date of the latest user visible feature addition. This is pretty fuzzy, so I'm open to other proposals.
👍 2
Vaibhavs10 commented 2024-02-12 12:26:24 -05:00 (Migrated from github.com)
Copy link

Hey hey! @Ryu1845 - thanks for taking this up!

Some thoughts on the release date: Maybe we take the date the model checkpoint was released?

This way we'll know when the ckpt was released and avoid having repos where there have been README code changes only?

Thanks again for taking this up, this is a very useful contribution to the community! 🤗

Hey hey! @Ryu1845 - thanks for taking this up! Some thoughts on the release date: Maybe we take the date the model checkpoint was released? This way we'll know when the ckpt was released and avoid having repos where there have been README code changes only? Thanks again for taking this up, this is a very useful contribution to the community! 🤗
Ryu1845 commented 2024-02-13 15:25:55 -05:00 (Migrated from github.com)
Copy link

Wdym by README code changes only? By user visible I mean features user has access to, e.g. ONNX inference in pflow-tts

Wdym by README code changes only? By user visible I mean features user has access to, e.g. ONNX inference in pflow-tts
Vaibhavs10 commented 2024-02-14 11:08:48 -05:00 (Migrated from github.com)
Copy link

Makes sense, I meant more like let's only track model releases instead of inference optimisations and so on. an example of this would be tortoise the original model was released in 2022 (I think) however the repo itself is quite active till now - mostly because of inference optimisations. Does that make sense?

Sorry for not being clear earlier. 🤗

Makes sense, I meant more like let's only track model releases instead of inference optimisations and so on. an example of this would be `tortoise` the original model was released in 2022 (I think) however the repo itself is quite active till now - mostly because of inference optimisations. Does that make sense? Sorry for not being clear earlier. 🤗
👍 1
Ryu1845 commented 2024-02-14 11:43:18 -05:00 (Migrated from github.com)
Copy link

OK I'll do that

OK I'll do that
Vaibhavs10 commented 2024-02-19 12:06:22 -05:00 (Migrated from github.com)
Copy link

Hey @Ryu1845 - let me know if I can help expediting this in anyway! I think this would be a really cool addition overall!

Hey @Ryu1845 - let me know if I can help expediting this in anyway! I think this would be a really cool addition overall!
Ryu1845 commented 2024-02-19 14:01:30 -05:00 (Migrated from github.com)
Copy link

Sorry, I've been busy these past few days. I'll try to get to it tonight. Feel free to take it up if you want, though.

Sorry, I've been busy these past few days. I'll try to get to it tonight. Feel free to take it up if you want, though.
Ryu1845 commented 2024-02-23 13:32:10 -05:00 (Migrated from github.com)
Copy link

I'm really busy these days, sorry for the lack of updates. I'll try to do this when I have the time, but someone can take it up if they want to.

I'm really busy these days, sorry for the lack of updates. I'll try to do this when I have the time, but someone can take it up if they want to.
This pull request has changes conflicting with the target branch.
  • README.md
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin Ryu1845/release-order:Ryu1845/release-order
git switch Ryu1845/release-order

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff Ryu1845/release-order
git switch Ryu1845/release-order
git rebase main
git switch main
git merge --ff-only Ryu1845/release-order
git switch Ryu1845/release-order
git rebase main
git switch main
git merge --no-ff Ryu1845/release-order
git switch main
git merge --squash Ryu1845/release-order
git switch main
git merge --ff-only Ryu1845/release-order
git switch main
git merge Ryu1845/release-order
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Vaibhavs10/open-tts-tracker!27
No description provided.