I don't want to hold up 1.4.0 to get the Avro<>Pig stuff in there, that needs a lot of review and some refinement. It would be nice, but is not nearly as important as the other stuff in this release.
I think we may have to move https://issues.apache.org/jira/browse/AVRO-545 into 1.4. Our Java dependencies are a mess and we should be producing more refined jars -- 'core', 'mapred', 'devel', etc. This not only helps prevent circular dependancies, but also helps projects choose the feature subset they are interested in and not carry the baggage + dependancies of what they are not using. As a part of the pig work, I will look into producing multiple jar outputs and cleaning up our Java dependancies in the build. -Scott P.S. Anyone ever on the IRC chat? I've tried several times to find it and never seen the channel listed, let alone anyone in it. Is http://avro.apache.org/irc.html correct? I've managed to get this far in life as an IRC noob, so it could be user error :) On Jul 19, 2010, at 1:05 PM, Doug Cutting wrote: > I'd like to make a 1.4.0 release of Avro in the next month. > > The list of unresolved 1.4.0 issues is at: > > http://tinyurl.com/avro140todo > > Can developers please look at this list? > > If there are issues that you're assigned that you don't expect to fix > soon, please unset their fix-version. > > If there are issues that you feel absolutely must be fixed in 1.4.0, > please mark them as blockers. > > Thanks, > > Doug
