Re: [rdiff-backup-users] Bump major release version for rdiff-backup?

[Eric Lavarde]

Hi,

On 12/08/2019 17:09, Otto Kekäläinen wrote:
> Hello!
>
> I've today bumped master branch version to 2.0.0, so all dev builds from 
> now on say they are version 2.0.0.
>
> Naturally no 2.0.0 will be released until a commit is tagged in git as 
> r2.0.0 (or v2.0.0 or just 2.0.0).

A few things to this, some important, some less:

1. you don't need to put me in copy, the list is fine, I'm on it.
2. I think it would be good to have everybody work with pull requests 
and protect master from direct changes. This is the way I learned 
guarantees the most quality and allow discussions before changes are 
actually made. It also makes sure that changes are serialized.
3. Would have this happened, I would have raised a few concerns:

a. there are a few more places where the version is kept (not nice, I 
know, see [1]), like Globals.py and the CHANGELOG
b. I don't like having the final release version in the repo too long 
before release, because some people might install from Git and it gets 
confusing which version they're actually using, for example if they ask 
for help.

Could we agree to revert to 1.9.0 until we have a better agreed solution?

Thanks, Eric

[1] https://github.com/ericzolf/rdiff-backup/issues/8

PS: and, yes, I need to move my issues to rdiff-backup but it seems I 
can't move them, only re-create them *sigh*