While we are working on the last remaining 1.2 issues, I wanted to
discuss some immediate tasks following 1.2 final release. Here is my
list.
1. Promote it! Lots of work went into the new release, so please
spread the word, via a blog or some other means. Cayenne 1.2 is a
much better Cayenne, has lots of new features, more flexibility,
improved tools, new documentation, and new home in the incubator. We
have something to be proud of :-)
2. Migrate to Apache package naming and license. I've heard some
conflicting information at ApacheCon Dublin that the new soon-to-be-
published Apache policy does not require the Apache license header in
the source files. This may simplify the task. (I can't find an
earlier message, I think from Jean, clarifying the procedure for the
code contributed by people whom we couldn't track).
3. Create a 2.0 branch and do a 2.0 release through the incubator.
4. Migrate the HEAD to Maven, splitting it in logical modules
(including the Modeler).
**** Finally the immediate coding tasks (that are high at least on my
own priority list) ***
5. Remove all deprecated API out of the way
6. Switch CayenneModeler to platonos plugin engine. There were some
concerns regarding Platonos (and we may end up maintaining it on our
own), but I haven't seen any workable alternatives proposed.
7. Work on the integrating into Geronimo things that we already have
on the JPA end. Even if we do not provide the full spec yet, I think
it is very important if there is way to build Geronimo with Cayenne
provider. I think it actually makes sense to do that both inside and
outside of OpenEJB (which will be the full provider of JSR-220), as
people who will use JPA often (almost always? :-)) do not care about
the "classic" EJB support.
There have been some volunteers to help with (2), (4) and JPA in
general, so I am taking on a cheerleader role here and asking who
wants to help (and ready to actually spend time) now that we are
ready to start all this work? ;-)
Cheers,
Andrus
