Elliot Metsger wrote:
[EMAIL PROTECTED] wrote:
I am very much against moving toward a 1.2.0 release. We should not
get mired in a 1.2.x release cycle of a JSR-168 impl. We need to
start moving toward jsr-286. The jsr-286 EG will be releasing a
public draft soon that is feature complete. Torsten's work in the 286
branch has almost caught up with the draft spec. Both Exo and JBoss
portal has preliminary (alpha/beta) jsr-286 releases. We should not
be that far behind.
When, assuming this is a goal, is a good time for 286 to get promoted to
trunk? And if so, what is the best way to go about doing this?
Backporting 286 patches from the branch back to trunk?
Whether in the trunk or not, I think adding Java5 Support (and generics)
to the 168 container is a good baby step towards 286. We had also
talked about adding jaxb bindings, etc. . .in 1.2.x. I'm very
interested in keeping this going, but am fine with it taking place in a
branch if that's the communities preference. My preference would be for
all of us to hammer out a 1.2.x and then move on, but given how slow we
move sometimes, I can understand why some people would like to jump
straight to 286.
David
