> > no, because 2.1 will be a patch release of 2.0, just like
> > 1.6.1 was a patch release of 1.6. There will never be a
> > 201rrpp00 for current, the next current will ne 399rrpp00
>
> Okay, got it now. So in short, we don't have any minor releases anymo=
re?
> We have just major releases and patches?

Nope.  There are concrete plans to make a separate "security/critical"
branch based on each minor release, and we'll probably see a 2.0.1.

> Interesting concept. I guess any change in systems calls, or other su=
rgery =

> now means a new major release then. Hmm, any feature extensions shoul=
d =

> also mean a new major release. What else?

The rules have always been a little bit blurry in this area with
respect to what is allowed to be pulled up and what isn't.  I think
the main thing is that it should not be too invasive, and should cause
a minimum of backward compatibility issues (with a strong preference
to "none").

Regards,

- H=E5vard