For the interpretive Java implementation, the current proposal is:
1) Fix a few issues we really aren't happy with. 2) Release 2.1.D12 and make it our official "release candidate". I hope to do this next week, if (1) permits. 3) Freeze the code for a while and let folks test it thoroughly. Exact duration of testing period to be determined. 4) If it passes the test period without unacceptable bugs surfacing, 2.1.D12 would then be renumbered to become our next official non-developer release. If bugs appear which can be fixed in a way that is not considered destabilizing, 2.1.D12 plus those fixes would be released. If fixes are large enough that we're worried about them, we'll probably advance to D13 and try again from step (2). I don't know what schedule is being proposed for the XSLTC or C++ sides of the project. If XSLTC, in particular, has something they Really Want to get into this release, we might need to adjust the schedule to allow for that. Or, to put it briefly: "Please be patient; we're making mistakes as quickly as we can!"
