It is not the new feature that may break something is it the implementation. For example I had to rewrite a lot of code to make sure modules in applications bytecode compiled "before" this new feature still run at all. I have not done extensive tests that this is correct (although I think so).
On May 1, 10:40 pm, Bruno Rocha <rochacbr...@gmail.com> wrote: > On Mon, May 2, 2011 at 12:25 AM, Massimo Di Pierro < > > massimo.dipie...@gmail.com> wrote: > > It works for me but under the hood there were a few changes. > > > We need to make sure that indeed we did not break anything and in > > particular we did not break backward compatibility. > > For me this does not breaks compatibility unless there are people using > subfolders for order execution arrangement. (which is not a documented > feature, and not a recommended practice) > > Developers will need to think twice when modeling applications for choosing > what to put in specific folder or not, but this matters only for bigger or > componentized apps, small apps and prototypes or legacy apps would have just > to work on the old way (all models on root folder). > > In the future, a routed approach will be a better way to define which model > needs to be executed for each controller request. > > The automatic update will not breaks because it does not update user > applications.
