Repository navigation
Replies: 2 comments
|
There's no announced date or milestone that I can find (the repo has no milestones), but the release history gives a rough idea:
So stable releases have come roughly every 4–7 weeks, and the latest nightly is from Sep 29. That puts the next stable "due" by the usual rhythm, but it's up to the maintainer. The easiest way to not miss it: on the repo page click Watch → Custom → Releases. You'll get a notification only for new releases, not for nightlies' commits or issue traffic. |
|
@SadieVane Hey, thanks a lot for the kind words, really appreciate it! I don’t use milestones or set specific dates right now. I try my best to ship new releases within 4 to 7 weeks max, but since I’m a solo dev and the only maintainer of Flow, it can take a bit longer sometimes, especially when YouTube changes something and breaks stuff, which can set me back a couple of days. This release also took longer than usual because it’s the biggest update Flow has ever had. Basically everything changed: all the screens were rewritten, there’s a fully optimized new tablet layout, a ton of new features, music recommendations, and native extraction instead of NewPipe’s extractor, plus a lot more. It took more than 400 hours of work since the last release, around 10+ hours a day. Current stable is v2.2.1, and the next one will be v3.0.0. It’s coming this week, so somewhere between today and Sunday depending on when I’m done with the last fixes and testing everything. If you don’t want to miss it, @sknoyon324234234234’s tip works great: Watch → Custom → Releases. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi, do you have an approximate timeframe in mind for the next stable release? I’m asking because I prefer not to use nightly builds, and I couldn’t find a planned release date in the project’s milestones. If you’re not already using milestones for this, they can be a handy way to share the target for an upcoming release. But no worries if you prefer a different approach.
And thank you so much for creating and maintaining Flow. It’s clear that a lot of thought and effort has gone into the project, and I really appreciate having a tool like this available. Thanks for all the time you put into improving it and supporting the people who use it!
All reactions