On 9/11/07, Aaron W. Hsu <[EMAIL PROTECTED]> wrote: > Hrm, I think this clarifies one thing... > > [EMAIL PROTECTED] said: > > 1. Once you run a -current, you cannot go backwards. This is repeated > > over and over in the FAQ. > > 2. New features do not get moved into -stable. > > I was under the impression that the current snapshots were still under the 4.2 > heading, and as such, were not actually ahead of the 4.2 release. I guess I > misunderstood here. Of course, I'm well aware of the particular FAQ. :-) > > The new features I am talking about are not the features after stable, but the > feature list that is currently listed in 4.2. Those are features that I want > to use now, but I want to make sure that I can move easily to 4.2-STABLE when > it is released. Are you saying that there is no way for me to get the features > in 4.2 now without running -CURRENT, which will require me to reinstall (as > opposed to upgrade) when 4.2 is released?
If you're running recent snapshots then you are running -CURRENT and as Theo mentions above: "...but beware since -current is now ahead of what the upcoming release will be, and that may not be what you want -- almost a thousand commits have already happened to it." -RELEASE would have been sent to the presses awhile back and development continues on from 4.2. You're past that point. The options are to continue with -CURRENT or start fresh with -RELEASE. Greg -- Ticketmaster and Ticketweb suck, but everyone knows that: http://ticketmastersucks.org Dethink to survive - Mclusky
