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.
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. I have not seen Execution context thing but still I can say its more native to Ofbiz framework and qualifies to be in trunk more then webslinger (I have nothing against it). Thanks and Regards Anil Patel HotWax Media Inc Find us on the web at www.hotwaxmedia.com or Google Keyword "ofbiz" On Apr 6, 2010, at 5:03 PM, Adrian Crum wrote: > Anil Patel wrote: >> I was thinking, Why not other way round. As I understand, we will not be >> able to use execution content features in other parts of Ofbiz in time for >> 10.4 release. If this is the case then additional code in release branch may >> add some new issues but will not add any benefits. Right? > > Have you even looked at the design document or the code? > >> So IMO we should wait till 10.04 release branch is created and merge >> executioncontext20091231 with trunk after 10.04 release branch is created. > > Okay, let's wait and then we will add the new issues to the 11.x release. > Oops, we better not do that - let's hold off until 12.x... > > Do you see where this is going? We already have Webslinger in the project - a > feature that isn't finished and isn't used. Has that caused problems in 9.04? > > -Adrian >
