On Thu, Mar 18, 2010 at 11:07 AM, Raymond Feng <[email protected]> wrote: > Hi, > > It seems that the official otest suite has latency to fix some of the > issues. Should we consider the following option to get Tuscany otest build > stable? >
I'd rather have better turnaround from OASIS, but I think we should fallback for the plan B and have a way to provide better ways to have "Tuscany local" fixes while we wait for the official OASIS version of the fix. > 1) Check out the latest otest from oasis svn > 2) We maintain a patch with changes on the otest that are not handled by > OASIS yet > 3) Have the build to apply the patch before the otest build > What is best ? Having the build to apply a set of patches (which will require the "build infrastructure" + manual maintenance of the conflicts when fixes start to be available from OASIS) or something more manual where we have a local (to tuscany svn) version of the otest with all patches applied (a git branch would be very useful here) and then manually add/remove changes (TortoiseSVN would really help here too...) ? Thoughts ? -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
