Am 18.04.13 08:00, schrieb Lukasz Lenart: > A new plan :D > > Plan for Struts 2.5: > Request Git repo from INFRA > Import project > Remove deprecated plugins > Drop support for Struts 1 (remove plugin) > Remove deprecated APIs > Switch to Java 1.6 > Rename XWork packages to org.apache.struts.xwork > Prepare the first release > > Plan for Struts 3: > Rename Struts 2 packages to org.apache.struts
What is the added value to expect Struts users to go through the pain of package renaming two times within a foreseeable time period? How about this big picture: 2.5 - intermediate step requiring users to cleanup their projects - switch to Git, remove all deprecated stuff, switch to J6 3.0 - new features and API with added value for users to switch to new API - includes alignment of all package names Regarding adoption I'm pretty sure that J6 should still be the way to go. J7 adoption seems to be around 15% right now as I read lately, maybe the next year helps to increase this rate. At least for 2.5 and start of development on 3.0 we should stay with J6 *sigh* > > > Regards > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
