Hi,
I can say with 100% certainty that:
- ASF source releases cannot contain compiled code (jars, dlls or the like)
- ASF source releases cannot include Category B code compiled or not compiled
- ASF convenience binaries can contain Category B compiled code
In various roles at the ASF including P
> Including Category B binaries in a source release is mentioned in ASF policy
> here [1].
Sorry to keep banging the same drum, but I read this before our earlier emails,
and if this is the intended meaning it needs to be rewritten. I also doubt this
was the intended meaning of the original aut
Hi,
> This is a known problem. Please help out.
That is the reason of having those jars in the source release? Could it just be
replaced by a series of curl commands in a shell script?
I can help fix up the LICENSE and NOTICE files, but the inclusion of compiled
code in a source release is the
>
> A vote of this test build will be initiated within the next couple of
> days. All testing in advance of the vote is most welcomed.
>
CI pipeline run for this is at
https://ci-cassandra.apache.org/blue/organizations/jenkins/Cassandra-trunk/detail/Cassandra-trunk/395/pipeline
This build is cl
This is a known problem. Please help out.
It has been made mention of on most of the recent vote release threads, and
we have a ticket CASSANDRA-16391 open to deal with it (eta is immediately
after 4.0).
https://lists.apache.org/list.html?dev@cassandra.apache.org:lte=5y:VOTE%20lib
Hi,
> Again, I don't see this stated explicitly. Perhaps the guidance should be
> clarified if this is the intention?
Out documentation can be improved, PRs welcome. :-) It was thought that
something like this didn't need to be documented, but obviously it does. I'll
start a conversation on le
On Sat 27 Mar, 2021, 1:41 PM Benedict Elliott Smith,
wrote:
> > Because a source release could not contain compiled code
>
> Again, I don't see this stated explicitly. Perhaps the guidance should be
> clarified if this is the intention?
>
> On 27/03/2021, 01:59, "Justin Mclean" wrote:
>
> H
> Because a source release could not contain compiled code
Again, I don't see this stated explicitly. Perhaps the guidance should be
clarified if this is the intention?
On 27/03/2021, 01:59, "Justin Mclean" wrote:
Hi,
> Could you clarify why you think this is incompatible with ASF po
> I suggest you read the whole thread. The outcome was that it's OK to put jars
> in version control but not in a source release.
There was no outcome AFAICT? There was a suggestion that was explicitly
caveated as only a suggestion that required formal approval by VP Legal, which
does not seem
