I can say about the stability, as I use Syncthing extensively and the version 2 since day one. It had the database issue, perhaps upon migration, which lead the program to crash on my Raspberry Pi 2B with 1 GB RAM. At some point I noticed the issue, removed the database and let it rebuilt it cleanly, which did the job and fixed the issue. Plus, I made a swap partition just in case. Haven’t seen any other issues after that. That was DietPi distro, based on Debian.
I had no issues like that on Arch, but my Arch desktops, laptops, and servers are more powerful, perhaps they handled the migration better. I expect that this was some bug that was fixed later. Fedora still syncs, but I wonder when would they update the repo, or if that’s me that wasn’t attentive somewhere and I need to change the repo. Maybe they follow the topic closer.
As far as I can see it has not been updated and someone is working on it. https://bugzilla.redhat.com/show_bug.cgi?id=2355938
Why does it matter for you to have version 2.0 anyway? As far as I understand it is interoperable with previous versions. At least, I didn’t have any problems until now.
I was worried there might be some weird bugs, as all my other clients are on v2. But so far, I haven’t noticed anything wrong.
So it’s purely some kind of a mix of cargo cult and just the will to have the newer updated software everywhere. That makes little practical sense, but I’m still with this illusion of newer = better, on a subconscious level, I think. Plus, I wasn’t sure everything is correct as it is not updated for a long time, I thought perhaps some Debian repos ingrained into my Fedora!
I can say about the stability, as I use Syncthing extensively and the version 2 since day one. It had the database issue, perhaps upon migration, which lead the program to crash on my Raspberry Pi 2B with 1 GB RAM. At some point I noticed the issue, removed the database and let it rebuilt it cleanly, which did the job and fixed the issue. Plus, I made a swap partition just in case. Haven’t seen any other issues after that. That was DietPi distro, based on Debian.
I had no issues like that on Arch, but my Arch desktops, laptops, and servers are more powerful, perhaps they handled the migration better. I expect that this was some bug that was fixed later. Fedora still syncs, but I wonder when would they update the repo, or if that’s me that wasn’t attentive somewhere and I need to change the repo. Maybe they follow the topic closer.
As far as I can see it has not been updated and someone is working on it. https://bugzilla.redhat.com/show_bug.cgi?id=2355938 Why does it matter for you to have version 2.0 anyway? As far as I understand it is interoperable with previous versions. At least, I didn’t have any problems until now.
I was worried there might be some weird bugs, as all my other clients are on v2. But so far, I haven’t noticed anything wrong.
So it’s purely some kind of a mix of cargo cult and just the will to have the newer updated software everywhere. That makes little practical sense, but I’m still with this illusion of newer = better, on a subconscious level, I think. Plus, I wasn’t sure everything is correct as it is not updated for a long time, I thought perhaps some Debian repos ingrained into my Fedora!