Hi Tom,
I agree with what you are saying here.
My one comment is that often times, the reason why one might want to
get their patch incorporated into the source tree is so that it is
part of the next official release.
If not, then what ends up happening is that every time one upgrades,
one has to go through all of their patches and re-engineer how to
properly implement them.
This becomes a very painful process because:
1. Dojo releases come out so frequently.
2. There are so *many* changes in each release, especially with
widgets, where in my experience, I have had to do so many patches.
Sticking with an older, official release is also very problematic
because it is very hard to get community support when you encounter a
strange problem. The answer is always "get the latest from SVN".
Unfortunately for production systems with a lot of customizations and
dojo patches, this is just not feasible.
Now, as for #1, I am sure that as dojo matures, releases will become
less frequent.
Also, wrt #2, I am sure that a lot of the changes with each release
are in fact due to the problem you've identified here! (ie. being to
permissible with the community wrt patches).
But, I just thought I would put in my 2 cents from the perspective of
a dojo user.
-aaron
_______________________________________________
Dojo FAQ:
http://dojo.jot.com/FAQDojo Book:
http://manual.dojotoolkit.org/DojoDotBookDojo-interest@...
http://dojotoolkit.org/mailman/listinfo/dojo-interest
