I think it all depends on the amount of tck destabilization and how long
we think it might take to get things resolved.
IMO we should be thinking about releasing 2.2 soon. I'm all for getting
as much ee6 content included as possible ... but if too much breaks in
the tck it could take a long time to recover.
So I think this is a case by case decision. If we know something will
cause significant instability regarding tck then I think we should
consider branching 2.2 and let trunk continue with ee6.
Joe
David Jencks wrote:
I realize I've been assuming that we'll just develop ee6 features in
trunk and release 2.2 with a bunch or all of ee6 implemented. I have
some connector 1.6 stuff I'm about to commit....
This attitude might cause tck problems especially with signature tests.
On the other hand maybe we can get signature updates.
What do other people think we should do?
thanks
david jencks
