Github user srowen commented on the issue:
    Not that I know of. I believe it's reasonable to say that there's a valid 
open question, and a reasonable argument at this stage that the non-assembly 
artifacts are allowed. If a 2.0.1 release is happening shortly I don't think it 
should block.
    however the assembly still has to go at least, and the possibilities are 
the 'hack' I mentioned above, or somehow modifying the Python tests to not need 
the kinesis assembly, because that would mean the whole assembly module could 

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to