Anil Patel wrote:
I am really not against merging executioncontext branch with trunk. I don't see reason to include it in upcoming release branch if we will not be using it. And yes, even though Webslinger is not a good examples we can still say that, decision put it in trunk was made too early, but its just me.
Users can enable the new security design and convert their applications over to it if they wish. They will also have time to evaluate it and prepare for the eventual switch-over.
Merging of executioncontext will make more sense to me if our release policy allowed back porting of some features from trunk to release brach (Internally I will be doing it anyways). If such thing was allowed then I can include framework changes now and at later date back port related enhancements to the branch.
Why do we need to backport features? The only backporting needed will be bug fixes.
-Adrian
