You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Sean R. Owen (Jira)" <ji...@apache.org> on 2020/03/26 19:06:00 UTC
[jira] [Commented] (LEGAL-512) What is the best approach to release
a golang client
[ https://issues.apache.org/jira/browse/LEGAL-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067958#comment-17067958 ]
Sean R. Owen commented on LEGAL-512:
------------------------------------
The project still has source code, no? A tarball of that source is a source artifact that you can distribute via the ASF. What's the issue with just distributing that like every other project does?
> What is the best approach to release a golang client
> ----------------------------------------------------
>
> Key: LEGAL-512
> URL: https://issues.apache.org/jira/browse/LEGAL-512
> Project: Legal Discuss
> Issue Type: Question
> Reporter: Sijie Guo
> Priority: Major
>
> Pulsar PMC is releasing its first release for pulsar go client. [https://github.com/apache/pulsar-client-go.]
> Since the release don't create any artifacts but just cut a release tag. Per the ASF policy, "Every ASF release MUST contain one or more source packages, which MUST be sufficient for a user to build and test the release provided they have access to the appropriate platform and tools.". It requires one or more source packages.
>
> What is the best approach here?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org