https://issues.apache.org/bugzilla/show_bug.cgi?id=45397
--- Comment #1 from Helder Magalhães <[email protected]> 2008-12-18 03:30:25 PST --- (In reply to comment #0) [...] > (for example, I can think of the Java 1.3 > support removed somewhere after 1.7 was released and to which documentation > changes can start being harvested). Apparently this was already made effective (revision 701292 ( https://svn.apache.org/viewcvs.cgi?view=rev&rev=701292 ), revision 713578 ( https://svn.apache.org/viewcvs.cgi?view=rev&rev=713578 )). Nevertheless, this still makes sense in the scope of, for example: * Schedule future Java version drops (Java 1.4, Java 1.5, etc.) * Target major features which may need lots of work but are interesting to have before a conceptual release 2.0 (for example, an interesting feature which will not make it before releasing 1.8 but that would be interesting to have in 1.9). As no comment was made on this issue, I ask if this is hard to accomplish and/or not relevant. If so, I might try to create bugs such as "Drop Java 1.4 support", "Drop Java 1.5 support" (to use as blockers) whenever possible and defer the version scheduling for the future... -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
