avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Blue (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1747) JavaScript implementation
Date Thu, 22 Oct 2015 17:35:27 GMT

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

Ryan Blue commented on AVRO-1747:
---------------------------------

I don't think there would be a need for two distributions, assuming that you mean an Apache
release and a release from your current github project. We would release using the Apache
process (release candidate, vote) and work would take place on Apache infrastructure. Otherwise
we would risk getting out of sync.

The release process itself is pretty simple. When we want to release a version of the software,
we usually get everything in that we need to and then build a release candidate. That's a
signed source tarball that everyone can verify. Then we have a vote where that tarball is
checked by project members. When that vote passes, we release the software. It's a bit more
involved than spinning your own release whenever you want, but that's for good reason.


> JavaScript implementation
> -------------------------
>
>                 Key: AVRO-1747
>                 URL: https://issues.apache.org/jira/browse/AVRO-1747
>             Project: Avro
>          Issue Type: Improvement
>          Components: javascript
>            Reporter: Matthieu Monsch
>
> Hello,
> I'm not sure if there is still interest in a JavaScript implementation of the Avro spec,
or if this is the right place for this message (apologies if not), but in case it's useful
here is one: https://github.com/mtth/avsc
> It's pretty fast, fully featured aside from protocols (AFAIK), and runs in the browser.
> Disclaimer: I wrote this library. (I initially searched around for existing implementations,
and even saw a few tickets on this board about JavaScript decoders, but couldn't find one
to support the schemas I have to process.)
> Best,
> -Matthieu



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message