AVRO-230 (shared directory with test schemas) would be great, but I'm not
sure it's a blocker. Do we want to make AVRO-570 (Python implementation of
MapReduce) a blocker? I can see the pros (suss out sharp edges in the
implementation) and cons (it's a new feature that's going to take a bit of
work to implement).
I've added AVRO-588 (Avro usable and testable on Python 2.4). I'll need to
augment the Python RPC to handle system errors correctly after AVRO-573 goes
in, so I've filed AVRO-599 as a blocker as well. Lastly, I've been meaning
to get to AVRO-528 (Twisted support) and AVRO-283 (change Python
implementation from dictionaries to objects) forever, so the release seems
as good as ever.
If anyone has Python chops and wants to help with the release, please
volunteer now! I'm also in IRC as "hammer" all day.
On Mon, Jul 19, 2010 at 1:42 PM, Scott Carey <[EMAIL PROTECTED]>wrote:
> 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
> 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.
> 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