On 11 May 2011 13:00, Jörg Schaible <[email protected]> wrote: > Hi Simone, > > Simone Tripodi wrote: > >> Hi all guys, >> as you maybe already noticed, we started working on OGNL codebase, I >> some question that PMCs/Mentors can help to reply: >> >> * is it fine updating groupId to `org.apache.commons` and artifactId >> `commons-ognl` even if under incubation? > > +1
I'd be inclined to keep the current package name and Maven ids during (most of) incubation. While the code is still incubating, I think it would be OK to break compatibility without forcing a package name change or Maven id change. Once OGNL is accepted into Commons, we need to be much more careful about backwards compatibility. Changing to the final names now might force another change if the API needs to be changed later. >> * version number: there are 2 way of thinking about it. For someone >> is fine continuing from the old version number, IMHO it should be >> 0.1-incubating, since in my mind ognl != commons-ognl. Which one >> sounds better? I tried to see how running projects managed that >> situation, once under Apache incubator, but didn't have success. >> Thoughts? > > I'd continue with the next major release number. Actually users don't really > care about, where the project is hosted, for them it's still ongl. You would > have been surprised also if Subversion started over with 1.0 again, didn't > you? > >> * it sounds reasonable to me plug the commons-parent pom to OGNL pom, >> WDYT? > > Definitely. > >> Many thanks in advance, all the best! > > Cheers, > Jörg > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
