Thanks for the clarification, Mark. I've heard about some umbrella JSR for each release of the JDK before and I was hoping that my proposed change could be covered as part of it. Thanks for confirming that such aggregation is possible.
> With regard to this particular proposal, as the original author of ... OK, I can promise that I will work hard on polishing my proposal. I can improve the code, I can add more documentation, I can write more tests, change the new API semantics, etc. I just need a sponsor to tell me what to change and where and then take and apply my final patch. Thanks in advance for your help. -jst Dne Friday 17 October 2008 06:24:13 Mark Reinhold napsal(a): > > Date: Fri, 17 Oct 2008 05:56:13 +1000 > > From: [EMAIL PROTECTED] > > > > If this is a modification to the API not just a patch for the > > implementation then the short answer is No. > > Well, not exactly. > > > API changes have to be made > > via a JSR. > > ... or in a Maintenance Review of an existing JSR. > > Small API revisions and additions do not require their own JSR; that > would be ridiculously inefficient. Instead we roll them up into a > series of Maintenance Reviews of the previous Platform JSR [1]. > > There have already been many small API changes in the JDK 7 codebase. > Suggested patches for further such changes are welcome, and will be > discussed and judged on their own technical merit. All implemented > changes will, in due course, be aggregated into an appropriate JCP > Maintenance Review. > > With regard to this particular proposal, as the original author of > the class in question I suppose I should have an opinion about it, > but that's a topic for a different message. > > - Mark > > > [1] > http://weblogs.java.net/blog/mreinhold/archive/2006/03/mustang_mainten.html
