avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruce Mitchener (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-358) Specify "levels" of Avro implementation in the spec
Date Thu, 03 Jun 2010 04:57:58 GMT

    [ https://issues.apache.org/jira/browse/AVRO-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874946#action_12874946

Bruce Mitchener commented on AVRO-358:

Instead of trying to come up with "levels" of the implementation based on various features,
I think we should unify the desires driving this with the discussion of having "Avro Enhancement
Proposals" or AEPs, based on the PEP process from Python.

At that point, each AEP can be updated with information about the support for that AEP in
each of the implementations.

Things can also be moved out of the spec itself and into separate AEPs (or have discussion-style
AEPs which provide additional information useful for the implementor).

I started drafting an email about this for the dev list, I will try to finish that up this
week and get it out for some further discussion.

> Specify "levels" of Avro implementation in the spec
> ---------------------------------------------------
>                 Key: AVRO-358
>                 URL: https://issues.apache.org/jira/browse/AVRO-358
>             Project: Avro
>          Issue Type: Improvement
>          Components: spec
>            Reporter: Jeff Hammerbacher
> We've discussed on IRC having well-defined "levels" of implementation for the Avro spec,
so that we can track the maturity of an implementation in each language. We should get to
work on specifying these levels more precisely and writing them into the specification.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message