Issues to address to get out of beta

[ts678]

@BlueBlock

if the user followed the installation instructions.

Duplicati 2 came out in 2014. The mono directions might be from March 2018, per What about a manual?

@BlueBlock

On the Windows side for the user there is little difference between 452 and 462.

Based on that, making users maybe advance mono by 27 months (some risk/work) seems like a net loss.

@BlueBlock

I’m not sure how it impacts scheduling if we’re talking about going to 452 versus 462.

.NET 4.5.2 target might be safe enough to run on old mono without taking time to go heavy-warnings route. Agree that canary testing lots of updated libs would take awhile either way, so still hoping for basic aftp fix.

@BlueBlock

And I’m not sure I really understand what impact to scheduling you are seeing.

Detailed in “Update framework to 462” PR. Biggest delay is if the warn-before-requiring-it plan is deployed.