Congratulations Berenguer!!
On Thu, Mar 25, 2021 at 6:18 AM Paulo Motta
wrote:
> Congratulations Berenguer, well deserved! Happy to see the project
> recognizing more contributors!
>
> Em qui., 25 de mar. de 2021 às 10:09, Brandon Williams
> escreveu:
>
> > Congratulations Berenguer! Thank you
Congratulations Berenguer!
- Yifan
> On Mar 26, 2021, at 11:49 AM, Sumanth Pasupuleti
> wrote:
>
> Congratulations Berenguer!
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: d
The test build of Cassandra 4.0-rc1 is available.
sha1: 2facbc97ea215faef1735d9a3d5697162f61bc8c
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-rc1-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1234/org/apache/
Hi,
I took a look at the source release and notice a couple of things from an ASF
policy point of view:
1. The LICENSE file may or may not include a list of things that are bundled in
the source release.The license seems to refer to 3rd party dependancies rather
than what is actually included
Just adding more congratulations, Berenguer! Well-deserved!
Lorina Poland
e. lor...@datastax.com
w. www.datastax.com
On Fri, Mar 26, 2021 at 12:17 PM Yifan Cai wrote:
>
> Congratulations Berenguer!
>
> - Yifan
>
> > On Mar 26, 2021, at 11:49 AM, Sumanth Pasupuleti <
> sumanth.pasupuleti...@gm
Hi,
I noticed the download page [1] contains links to convenience binaries but not
to the actual release. I can see that the source is in the place on the mirrors
but there's not an obvious link to it.
When I did download the the 3.11.10 release [2], I can see that it contained
compiled binary
(mostly reiterating) +1 to branching and unfreezing trunk, and to codifying
the release cadence.
Excited about the 4.0 rc! and looking forward to the roadmap discussion!!
On Thu, Mar 25, 2021 at 8:18 AM Paulo Motta
wrote:
> > My thinking was talking about when to lift the freeze was moot if we
>
> When I did download the the 3.11.10 release [2], I can see that it contained
> compiled binary files (jars), which I don't think is in line with ASF release
> policy.
Could you clarify why you think this is incompatible with ASF policy? AFAICT
the policy only stipulates that binary releases _
Hi,
> Could you clarify why you think this is incompatible with ASF policy?
Because a source release could not contain compiled code (category A or
otherwise), if it does then it not open source. See for instance [1]. This is
why tools like Apache Rat look for certain types of binary files in r
To quote Niclas in the legal thread:
The notion that these jars are "not open source" and must therefor not be used
in the way they are intended is a preposterous stance
This seems to genuinely be against policy in a way that is profoundly
frustrating: the source of the project is available, th
HI,
> The notion that these jars are "not open source" and must therefor not be
> used in the way they are intended is a preposterous stance
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.
This has been discussed sev
11 matches
Mail list logo
