Ondrej, thank you for packages! Sysadmins everywhere appreciate them greatly (including myself and MBIX).

On Wed, May 23, 2018 at 9:27 AM, Jan Maria Matejka <jan.matejka@nic.cz> wrote:

I suggest this way:
1) rename bird -> bird-legacy and bird-devel -> bird2
2) keep this for quite a long time to let users manually change from bird-legacy
to bird2 (one whole release cycle?) and not force them into upgrade
3) rename bird2 -> bird
4) drop bird-legacy when we stop supporting it

This is too complicated, in my view.

Do it like apache.

Leave the bird 1.x package as bird

Add new bird 2.x package as bird2

In future, bird 3.x can bird3

No need to change package names, fewest surprises to sysadmins.

Cheers,

Jonathan