8 hours ago
(9 hours ago)raulo1985 Wrote:(Today, 10:03 AM)kaft Wrote: You really should've taken more time and testing on these releases.
Its a major release with breaking changes, and you are not a small, selfhosted app anymore.
This project is free, we get a top notch alternative to paid projects like Plex (an even better alternative tbh), and the devs don't earn anything besides donations. Besides, this particular release included a major database change and it was posted all over the place that bugs were obviously expected with first releases. You can't expect a major change to not have bugs, specially when released to the general public with countless different setups. Being a big project now doesn't make them owe us anything. THis is a community project, if there are bugs, you should report them to help troubleshooting, telling the devs they should test their releases more before releases will only drag the project down (bugs reported by general users are key to the project's success). Like the previous post said, that was uncalled for.
Hello All,
I just register to add one comment, here it is : As I understand the principles of release/bugs/solving cycle in the small microcosm of open-source, once you become a largely distributed solution working for millions of users, you have to take care of the publicity and rumors when you release a new version. Your solution is now at a point where it grows because reliable or it fails because bugs making an average user not able to see his/her favorite movie tonight. If it fails, he/she will simply change of solution and never go back.
BR
