| [ee4j-community] JCP or not (fork of Re: On Naming) |
| The JCP process and minimal turn over is relatively slow. - when integrating one spec with another, it usually goes as fast as the slowest (could be improved within the JCP rules as it’s more organisational in nature) - there is a general black hole in lieu of feedback during the feedback phases - there are a bunch of non parallelizable steps (especially the feedback phases), this forces to do retroplanning and freeze work weeks before it becomes available - when Russian dolling specs, the retroplanning explodes quite a bit - there is no formal way for users to try WIP / newer specs, this leads to few to no feedback on it until the full Java EE is out. - the “if you screw up it’s forever” strong backward compatibility guarantees also means we are thinking hard and long about things and go on the conservative side. - updating the JCP process itself is a very long process BV 1.0 took I think between 1.5 to 2 years. That’s not what I would call a good pace :) Doing a 3 months increment on a spec would mean too little (work time) / (total time) ratio. I’m sure that’s not exhaustive and others might have a different view. Emmanuel
|