Great new feature: Restore file from S3 delta backup!

Andrew

@olivierlambert I take a nap for hour and things explode!

This discussion is half flame/half a lesson on dealing with bleeding edge code frustration. It might be worth changing the subject to "Unexpected restore feature change" and move on to a new thread with a more official restore announcement that includes reasons for the change/improvement, known ARM issue, and a workaround to use the legacy restore option.

For such a large code change it might have been good to release it as a branch for public testing first, but that may not uncover issues as quickly as a surprise brute force feature improvement.

As for my experience with new features that cause problems, I report them, try to understand what's wrong and why, and help resolve the issue. I have more than one copy of XO and just use a working one that I don't upgrade while the new feature is fixed. VMs are "free" so just add another. It's opensource and the community is the end user, tester, and developer. If you need a stable version of XO then use XOA or don't update to the latest commit. And if you do update, and it fails then revert to a working version.

olivierlambert

To sum up my feeling, I found it very insulting when people using something for free, had behaviour that even paid customer haven't when they had a problem. You have somehow the right to be frustrated against people building a paid service that broke (but you can still be polite). If it's truly free and collaborative, then you have to make an effort to improve the situation and being constructive, because nobody owe you something.

After years of managing XO customers and community, I found a clear relation between how much you pay for a service and the way you treat humans behind that service. Some people are grateful (I would say almost everyone here and that's great!) and some are behaving in a way that making you regret to share all your work entirely for free. Luckily, they are a minority, and that behaviour should be discouraged.

mavoff

@olivierlambert I am sorry if you felt I came on too strong, didn't mean to, neither I think it was all that. But honestly it saddens me that you got all riled up on this cause I do appreciate a lot the work you guys do here, and I've always appreciated you. Have a nice one!

olivierlambert

If I felt that way and we never had issues in the past, it's maybe for a reason. I'm a very patient person (as you can read since years here). So you shouldn't be saddened but more trying to understand something you provoked (it's still not clear that you understand it). I think it's important to know when not to push too far, and you were clearly too far

Next time you are frustrated on an open source software you use for free (likely in production otherwise you wouldn't have been that frustrated), remember that being kind will be more productive in the end. This will be better for everyone.

Also I hope it's more clear for you that using things on master was never meant to be under our internal QA since it's not a controlled environment (but it's documented with big warnings. Maybe I'll make it even more clear in the doc, I don't know, I'm surprised you didn't get it since you are using it since a while. Maybe this misunderstanding explained part of your frustration).