[
https://issues.apache.org/jira/browse/AVRO-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877520#action_12877520
]
Doug Cutting commented on AVRO-482:
-----------------------------------
I'm not sure what the issues here are. Apache requires that we vote on the
sources of a release. It's fine to generate new binaries after a release vote,
so long as they use the sources that were voted on, even binaries distributed
by Apache as officially released binaries. Dunno if the tarball you can submit
to PyPI would contain modified sources, but, if it doesn't, you're fine to
create and submit something for 1.3.3 now, after the vote.
> Improve and standardize process for publishing Python release artifacts to
> PyPI
> -------------------------------------------------------------------------------
>
> Key: AVRO-482
> URL: https://issues.apache.org/jira/browse/AVRO-482
> Project: Avro
> Issue Type: Improvement
> Components: python
> Reporter: Jeff Hammerbacher
>
> We are now publishing Avro releases to PyPI. Let's make sure things work as
> planned.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
