-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Consider to release v0.10.0 #682
Comments
@theScrabi: Can we at least update NewPipeExtractor first now that it
supports decrypting URLs correctly again?
And how about multiple services? Or will we do that with the release after
v0.10.0?
|
I'm not a huge fan, of putting to much changes into one version. Because the more U change the more unstable it gets. Also I made the experience that user will find bugs you aren't aware of. I'd like to release now, and than stick to a constant release cycle again. (Before the huge refactoring of the extractor we had an almost every week cycle). We can consider multi service support in a few versions later, but not now. |
@theScrabi: I'm OK with releasing now, but only if we update
NewPipeExtractor first.
I'm not a fan of too much changes in one release either.
We already have it in NewPipeExtractor, btw I'm working on adding it to
NewPipe, but I've been really busy the last few days.
|
@mauriciocolli updated the extractor here |
I already updated the extractor 23f70d6. But one thing to always keep in mind when updating is the database. If we update carelessly we could end up clearing the database, which is not very cool. PS: It still have some annoying bugs in the extractor, so I wouldn't recommend release right now (YouTube has been changing in the past days). |
Oh, I didn't notice. But if there are some nasty bugs, I'd wait indeed.
|
This is why we should consider to have a beta app. Because there will always be bugs. Some people can get along with a few bugs some can't. If we have beta people could decide them selfs. |
@theScrabi: I agree, but what'll we do with version numbering?
|
I'd do it the way we do it now, just put a beta in front of the version. like (We'd have to put it in front because only this way fdroid can distinguish between beta and nonbeta) |
I saw that. Due to that new UI some of the things that still work are rather unclear if they will work in the future. But atm I'm more concerned of the database, because it would not be such a huge problem if the crawler stopped working while a new version is released. We then just hat to asap release a version that fixes that problem (happens to the past will happen to the future as well). @mauriciocolli: What in particular does not yet work? I couldn't find anything that drove me that crazy that I would not release yet. |
I fixed some error that caused these annoyances (at least the ones that I noticed), but just a brief summary:
They are very annoying because every time they ask the user to report (in almost every search, in every "next videos"...). |
Yea. I see. |
Although these are extractor related bugs right? I have to admid that It's not that bad. Over all NewPipe is pretty usable. So form my perception of user experience of usage I'd vote for release. Anyway is the database still an issue tho? |
Well, it was bad before I fixed them (asking the user to report to do the most trivial of things like search). The database was more of a warning about the fact that we'd have to create multiple tiny migrations, which is not ideal. But that will not be a problem anymore as we'll have a different build so we can see when it's the best moment to release. |
Well if its not the code, then there is nothing that can prevent us from release. |
So I've released: Shame on me if something went wrong. |
you are right :) removed it |
The version of NewPipe on fdroid hasn't updated I think |
Several apps on fdroid haven't updated yet. I don't know what takes them so long again. |
Can we now consider to release version v0.10.0?
Now where more or less all feature work stable enough to be usable.
The text was updated successfully, but these errors were encountered: