RE: Release Plan

[Eric Robinson]

Thanks, Eric (Z.), I understand now. I got confused for a minute because my 
name is also Eric, so I thought the message was sent to me by mistake. I 
eventually figured out that it was a general message.

--Eric (R.)

-----Original Message-----
From: rdiff-backup-users 
<rdiff-backup-users-bounces+eric.robinson=address@hidden> On Behalf Of EricZolf
Sent: Monday, November 18, 2019 3:31 PM
To: address@hidden
Subject: Re: Release Plan

Hi Eric,

I'm not sure how you mean this remark:

- if you fear to hear secrets not meant for users, do not fear! One, it's open 
source so there is nothing secret; two, it's also meant for users, because 
users are the best beta testers! And you're welcome to help!
- if you feel disturbed, we don't have a separate list for developers, we can 
have one if really needed, but it's not like we're generating a lot of traffic, 
and perhaps we can do without?
- if you meant something else, then I didn't get it :-P

KR, Eric

On November 17, 2019 10:05:59 PM UTC, Eric Robinson <address@hidden> wrote:
>Guys, not that I mind being included in internal discussions about
>rdiff-backup development (it's actually quite interesting) but I don't
>think you intended me to be in this discussion.  ;-)
>
>-Eric R.
>
>Get Outlook for Android<https://aka.ms/ghei36>
>
>________________________________
>From: rdiff-backup-users
><rdiff-backup-users-bounces+eric.robinson=address@hidden> on
>behalf of EricZolf <address@hidden>
>Sent: Sunday, November 17, 2019 3:29:10 PM
>To: address@hidden <address@hidden>
>Subject: Re: Release Plan
>
>Hi,
>good question, let me try to summarize the current state:
>
>- migration to Python 3 is finished, there are no  known regressions.
>- we've fixed a fair amount of smaller bugs and cleaned the repo
>structure
>- testing on Linux is done automatically and regularly so that I'm
>quite confident about the quality of the code on this platform
>- testing on Windows would need more love - anybody is welcome to test
>who can compile rdiff-backup
>- cross-platform testing is also a topic where we need testers
>- if nobody takes care of MacOS, it'll get dropped as an officially
>supported platform (we won't remove code, but it'll be by chance that
>it'll work)
>- the remaining enhancements we need for this release (mainly around
>CI/CD) are mostly addressed via on-going PRs, here Otto and Patrick
>must tell if they need support. There was little movement in the recent
>past.
>
>Writing these lines, I realise that I should try to generate a beta
>release (even if only manually) so that people can more easily test,
>without the trouble of compiling the code.
>Let me work on it, and come back to you.
>
>KR, Eric
>
>
>On November 17, 2019 10:59:14 AM UTC, Frank Crawford
><address@hidden> wrote:
>>Eric,
>>
>>Are you still looking at doing a release before the end of the year?
>>
>>If so, what items do you still need to complete, and can we help you
>>out with it?
>>
>>Regards
>>Frank
>
>Disclaimer : This email and any files transmitted with it are
>confidential and intended solely for intended recipients. If you are
>not the named addressee you should not disseminate, distribute, copy or
>alter this email. Any views or opinions presented in this email are
>solely those of the author and might not represent those of Physician
>Select Management. Warning: Although Physician Select Management has
>taken reasonable precautions to ensure no viruses are present in this
>email, the company cannot accept responsibility for any loss or damage
>arising from the use of this email or attachments.
Disclaimer : This email and any files transmitted with it are confidential and 
intended solely for intended recipients. If you are not the named addressee you 
should not disseminate, distribute, copy or alter this email. Any views or 
opinions presented in this email are solely those of the author and might not 
represent those of Physician Select Management. Warning: Although Physician 
Select Management has taken reasonable precautions to ensure no viruses are 
present in this email, the company cannot accept responsibility for any loss or 
damage arising from the use of this email or attachments.