William A. Rowe, Jr. wrote: > > Seriously, some of us will likely hack at this during the holidays, > and at some point, the version drift will be so great that it becomes > very hard to track down where breakage was introduced. > > 2.2.4 by early this coming week, followed by 2.2.5 after the holidays, > will make it easier to track down the offending changes (and possibly > give users a choice of versions - one of which doesn't have the flaw > they trip over.) >
Well, that was kind of my thought, is that people would have more time to play with 2.2.4-dev over the "break" and then I thought of the user community and whether it was "nice" to put out 2.2.4 a week before Christmas (causing them to upgrade) and then after the holidays having a 2.2.5 available and making them upgrade again :) I see your point 100% though... I really hoped that we would have had a 2.2.4 out sooner, but the votes didn't come as fast as expected :) But tell you what, if you want to do a 2.2.4 Sun/Mon then I'll do 2.2.5 mid-Jan (assuming there's enough for a release)... -- =========================================================================== Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "If you can dodge a wrench, you can dodge a ball."
