delijah said the following on 03/24/2011 03:39 AM: > Interesting point. Agree on the "final" stuff. > > We gonna use the milestones in development phase, but we need to build > a product and cannot spend too much time on fixing bugs inside of a > framework (so we not gonna use the trunk). Just some background here on how we develop the framework. We have a rather large test suite to test the framework via MXUnit. All nightly zips must pass all unit tests in additional to the Var Scoper tool. Core functionality such as event announcement and request handling has not been overhauled since Mach-II 1.5 and only small changes to that core functionality since then.
I believe you said the majority of the your application is going to be using endpoints. I believe you're going to have a lot of sore experiences if you limit your development to using milestone 2. A lot has changed in the endpoint feature since milestone 2 and we fixed many bugs / missing features in the REST endpoints in the trunk since then. To underscore my point, I just ran a diff between m2 and the trunk. The SVN diff file is over 3,000 LoC long. The only remaining tickets for m3 are related to the i18n (localization) feature. Core development on endpoints is done unless somebody makes a suggestion or discovers a bug that is unknown to us. At the moment, I know several places that are using the 1.9 nightlies on production including the fine folks at DaveRamsey.com which helped write a majority of the REST features. Honestly, I could easy just mark the current trunk as m3 today. As Matt was saying, it's pretty arbitrary... .Peter -- To post to this group, send email to [email protected] For more options and to unsubscribe, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en SVN: http://svn.mach-ii.com/machii/ Wiki / Documentation / Tickets: http://trac.mach-ii.com/machii/
