Dar Scott wrote: > However, I still want to emulate your daring do. I can take the > conservative approach you described during the day as the mild > mannered software developer, but at night, I can put on my cape > and jump into trying out DPs.
As I think about this more, given that the definition of "Stable" isn't in the dictionary sense but in the engineering sense of "no feature changes since last build", and given that all versions of 8.x carry fixes forward, I'm inclined to believe that the most robust build at any given time is usually the one most recently released.
Of course new features introduced in a most recent build will still need some testing to make sure they're solid, but any existing features should be as good or better than the last "Stable" build given that any fixes recently completed will be in the more recent build.
That doesn't account for regressions, but that's also a good argument to use the most recent build: any regression is one for which a test isn't already in the automated test system (they use a LOT of automated tools to check things before release). The sooner a bug is discovered and reported, the better for everyone.
-- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ____________________________________________________________________ ambassa...@fourthworld.com http://www.FourthWorld.com _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode