rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cross-platform backup tool First beta v2.1.2b1 release towards v2.2.


From: Robert Nichols
Subject: Re: cross-platform backup tool First beta v2.1.2b1 release towards v2.2.0
Date: Sat, 17 Sep 2022 18:59:20 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0

On 9/7/22 11:11 AM, EricZolf wrote:
Hello everybody,

This is a beta release so that many people can test before this becomes the next 
stable release. All changes are documented in the changelog 
<https://github.com/rdiff-backup/rdiff-backup/blob/v2.1.2b1/CHANGELOG.adoc#new-in-v2-1-2b1>.
 Check especially the changes (marked with /CHG/) which might impact your workflow. 
Since the last alpha:

   * support for Python 3.6 has been dropped,
   * return codes have changed and are now more detailed, see man-page
     for details,
   * more stability around failed file handling,
   * a lot of code changes under the hood (which you shouldn't notice but
     just that you don't think we were lazy),
   * and we even found some time for new features (only using the new
     API), like better locking of repositories and being able to regress
     the last backup even if it was successful, possibly one of the
     longest standing RFEs.

Please use this release to test and report issues 
<https://github.com/rdiff-backup/rdiff-backup/issues/new?assignees=&labels=&template=bug_report.md&title=%5BBUG%5D>,
 especially regarding:

   * usage in client/server in combination with version v2.0.5 of
     rdiff-backup
   * usage under Windows (and MacOS/X)
   * usage of the new API with |--api-version 201|

The only issue I'm seeing with a v2.0.5 client and a v2.1.2b1 server is that you 
(obviously, in hindsight) have to be using a command line syntax that both versions 
understand, which is the old syntax. That means the client sees a lot of unavoidable 
"deprecated" warnings, and also that future removal of that old syntax from 
v2.1 will break compatibility with v2.0.

--
Bob Nichols     "NOSPAM" is really part of my email address.
                Do NOT delete it.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]