![]() ![]() ⦁ Resolved a logging issue with trial expiring at the exact same moment The service, but the symptoms were scary. The problem is benign and restarting the UI would re-attached it to The UI wouldn't want to connect to it, insisting on running as a fullĪpp => it will show up unlicensed and with an empty list of jobs. ![]() The backup service would still run and execute all the backups, but Run in a desktop mode IF it is set to auto-start on Windows logon. (as in "several years"), R80.2 will erroneously assume that it needs to Older installations that were switched to the service mode a while ago ⦁ Resolved an issue with auto-launching the UI in service mode - with I'll post more details in the blog shortly as it's an That's the case (even though we no longer can sign new releases with This isīecause versions 80.1 and older expect the update package to carryĪ signature of "Pipemetrics SA", so we use some acrobatics to ensure Name of the company from Pipemetrics to IO Bureau.ĭo note that because of this change all existing installations exceptįor 80.2 will receive an update packaged in a special way. ⦁ Switched to using new code signing certificate - due to changing the Immediately before sending them to the remote end. Module now explicitly re-checks that all lines are CRLF terminated Looking at the code on our side there's no way this could've (allegedly) contained a lone LF character as a line terminator instead This has to do with a report of qmail refusing an email alert because it ⦁ Reworked email alerts module to double-check message formatting. Microsecond precision in timing, but apparently some installation _precisely_ when the job is being launched. Triggered when the dispatch of a "missed a backup run" alert ends ⦁ Resolved an issue with logging email alerting failures - an exotic issue ⦁ Resolved a cosmetic issue with the Welcome window - some text was Reparse point and if it's of a directory kind. The program will now correctly report the event both if it is a file That is, when running into a reparse paint _of an unknown type_ ⦁ Resolved an issue with reporting reparse points that are folders. ⦁ Configuration self-backup now covers additional config files. ⦁ Exporting configuration now also picks up email alert templates. If anyone is up to sharing their opinion, either con and pro, I'm all ears.⦁ Run-on-device-arrival scheduling now applies to local devices only -Īs opposed to being also triggered by a network share becoming I think this approach has a reasonable degree of fairness to it, but I also expect that it won't make everyone happy. unlimited access to all updates (at a steep discount), but that's TBD. Perhaps we'll have other options as well, e.g. After one year we'll have a paid-for option for extending the access for another year. When a bug is fixed, it will go into all applicable major releases and produce respective bugfix updates.įeature updates will be free for the first year. Maintenance updates will get sorted into two types - feature updates and bugfix updates.įeature updates are the major releases (79, 80, 81, etc), these will be adding new functionality.īugfix updates are the minor releases (79.1, 79.2, etc.), these will be, unsurprisingly, fixing bugs.īugfix updates will be free, no strings attached. Keep in mind that this applies to the new license types only. Updates - we are going to be reworking things here as well. We will be supporting 5 licenses types (2 existing and 3 new ones), but we'll be selling only new types. The licenses will remain perpetual and require no renewal. Licenses - we will be moving away from the use-based model to more conventional feature-based model. ![]() Now, that all said, we are going to be changing several things. If you don't routinely edit huge files, then you should have a look at the current versioning support. The difference between it and the "v3" versioning is in the handling of very large files. From what I've seen so far, existing versioning works really well for the vast majority of people who need it. That said, I would strongly suggest not to fixate on the "v3" part, because I am now leaning towards adding cloud support first, which will move git-based archiving support (the defining v3 feature) to the back burner. "Bvckup 3", if and when it comes around, is a separate product, so - no, there's going to be no free upgrade, but there'll be an upgrade pricing. "Maintenance updates" are all the updates released under the "Bvckup 2" name. At the moment, licenses are perpetual (require no renewals) and maintenance updates are both perpetual and free. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |