It is absolutely necessary. The whole point of the release branch is that we end up stabilizing code for release. There are numerous bug-fixes that we should not throw away.
On 23/08/07, Arnaud Simon <[EMAIL PROTECTED]> wrote: > > On Thu, 2007-08-23 at 14:19 +0100, Rupert Smith wrote: > > > > Also, is it really worth testing the low-level API separately to the > JMS? > > Unless the JMS layer is doing something really time-consuming, I imagine > > they will be very close. > > I imagine too, however we may want to test specific features of the > lower level API. > > > Did you just copy perftests on M2 onto trunk? I hope this does not > conflict > > when we recover those lost merges? > > I reflected the changes of M2 back into the trunk. > Regarding the merging, I was wondering if this is going to be that > useful. We have now a new code base for 0.10 client and will certainly > drastically change the broker implementation. So, I would say that for > now we may only want to merge common and broker. But the real question > is to decide if this is necessary. Any thoughts about that? > > > Also, one other thing that comes to mind, is that perftests on M2 are > using > > junit-toolkit-0.6-SNAPSHOT latestm, whereas trunk was pinned to an > earlier > > version. You may now wish to unpin trunk, to keep up with the toolkit > > latest. > > I am using the pom.xml file form M2 so it should be done. > > Cheers > > Arnaud > > >
