Le 05/12/2011 16:14, Christian Grobmeier a écrit : >> [+1] Yes, you may release the next major release of JEXL3 with a Java6 >> requirement
+1 > > I think the maintainers of a component can decide on their own which > jdk they want to support. If you want to support a newer Java with the > next big major version of JEXL I give you my +1. For me a major > version is allowed to break old rules and create new ones. Agreed. > >> PS: Is there a process to formally move a project from Commons to elsewhere >> within Apache? There is a general process for moving to attic, but I don't think this is what you want. I think there is also a general process to become a TLP. This is exactly what commons did some years ago, coming from Jakarta. Luc > > What exactly do you mean? Make JEXL a top level project or move JEXL > to another toplevel project? Or something completley different? > > To move JEXL out of here, i think you should make up a (good) proposal > and vote on this list. I can imagine it would go to the incubator to > build up an community. Anyway I tend to think a component should have > a pretty good size to stand on its own. > > Cheers > Christian > >> >> >> >> >> >> >> >> -- >> View this message in context: >> http://apache-commons.680414.n4.nabble.com/VOTE-Can-the-next-version-major-version-of-a-project-require-Java6-i-e-drop-Java-1-5-tp4160635p4160635.html >> Sent from the Commons - Dev mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
