-
Notifications
You must be signed in to change notification settings - Fork 70
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
Add release dates #27
base: main
Are you sure you want to change the base?
Conversation
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! 🤗 |
Wdym by README code changes only? By user visible I mean features user has access to, e.g. ONNX inference in pflow-tts |
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 Sorry for not being clear earlier. 🤗 |
OK I'll do that |
Hey @Ryu1845 - let me know if I can help expediting this in anyway! I think this would be a really cool addition overall! |
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. |
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. |
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.