Alexander Hall wrote: > Henning Braue wrote: > >>> > Is it possible to upgrade from 4.0-current to 4.1-stable? > >>> No... Thats what the above quote is trying to tell you. A -current >>> src tree is always the newest code; -stable is the original release >>> with patches. >> >> yayaya, but his 4.1-stable once upon a time was 4.0-current, so all is >> fluffy and he can upgrade (well, once 4.1-stable exists, i.e. roughly >> may 1) > > If I'm not wrong, the stable branch (e.g 4.1-stable) is not simply > branched from 4.1-current at a specific date or time, but rather a > selection of well-working parts thereof.
Wrong.... > If so, is it not possible > that some parts of the OP's 4.0-current system might have changes > that did not make it into 4.1-stable? > > /Alexander see the beginning of FAQ 5... (I seem to be saying this a lot lately. Yes, this section is full of all kinds of meaning, but it is really much simpler than people are trying to make it...) No, 4.1-stable is "branched" at /4.1-release/, which comes after 4.1-beta, and before 4.1-current. The only things that are in 4.0-current that are not in 4.1-stable/4.1-release are things that didn't work and got removed (or replaced or improved upon by something else or or...) X-release -> X-current -> X+0.1-beta -> X+0.1-release -> X+0.1-current ... HOWEVER, there ARE things in a recent 4.0-STABLE build which are NOT yet in 4.1-stable, because there are no 4.1-stable commits yet, and will not be until release day. AT THIS TIME, 3.9-stable and 4.0-stable are being maintained, but 4.1 is not. Jumping the gun on -release is not wise unless you understand why it isn't... Nick.
