Proposing the test build of Cassandra 4.0.1 for release.
sha1: 6709111ed007a54b3e42884853f89cabd38e4316
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.1-tentative
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1247/org/
+1
On Wed, Sep 01, 2021 at 12:54:36PM +0100, Sam Tunnicliffe wrote:
> Proposing the test build of Cassandra 4.0.1 for release.
>
> sha1: 6709111ed007a54b3e42884853f89cabd38e4316
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.1-tentative
> Maven Artifacts:
>
>
> The vote will be open for 72 hours (longer if needed). Everyone who has
> tested the build is invited to vote. Votes by PMC members are considered
> binding. A vote passes if there are at least three binding +1s and no -1's.
>
+1
Checked…
- signing correct
- checksums are correct
- source
+1
On Wed, Sep 1, 2021 at 4:54 AM Sam Tunnicliffe wrote:
> Proposing the test build of Cassandra 4.0.1 for release.
>
> sha1: 6709111ed007a54b3e42884853f89cabd38e4316
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.1-tentative
> Maven Artifacts:
> https:/
+1nb
> On Sep 1, 2021, at 6:54 AM, Jeff Jirsa wrote:
>
> +1
>
>
>> On Wed, Sep 1, 2021 at 4:54 AM Sam Tunnicliffe wrote:
>>
>> Proposing the test build of Cassandra 4.0.1 for release.
>>
>> sha1: 6709111ed007a54b3e42884853f89cabd38e4316
>> Git:
>> https://gitbox.apache.org/repos/asf?p=cass
+1
On Wed, Sep 1, 2021, 6:55 AM Sam Tunnicliffe wrote:
> Proposing the test build of Cassandra 4.0.1 for release.
>
> sha1: 6709111ed007a54b3e42884853f89cabd38e4316
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.1-tentative
> Maven Artifacts:
> https://re
+1
- Yifan
> On Sep 1, 2021, at 7:57 AM, C. Scott Andreas wrote:
>
> +1nb
>
>> On Sep 1, 2021, at 6:54 AM, Jeff Jirsa wrote:
>>
>> +1
>>
>>
On Wed, Sep 1, 2021 at 4:54 AM Sam Tunnicliffe wrote:
>>>
>>> Proposing the test build of Cassandra 4.0.1 for release.
>>>
>>> sha1: 670911
+1
On Wed, Sep 1, 2021 at 11:16 AM Yifan Cai wrote:
> +1
>
>
> - Yifan
>
> > On Sep 1, 2021, at 7:57 AM, C. Scott Andreas
> wrote:
> >
> > +1nb
> >
> >> On Sep 1, 2021, at 6:54 AM, Jeff Jirsa wrote:
> >>
> >> +1
> >>
> >>
> On Wed, Sep 1, 2021 at 4:54 AM Sam Tunnicliffe
> wrote:
> >>>
+1
On Wed, 1 Sep 2021 at 12:34, Joshua McKenzie wrote:
> +1
>
> On Wed, Sep 1, 2021 at 11:16 AM Yifan Cai wrote:
>
> > +1
> >
> >
> > - Yifan
> >
> > > On Sep 1, 2021, at 7:57 AM, C. Scott Andreas
> > wrote:
> > >
> > > +1nb
> > >
> > >> On Sep 1, 2021, at 6:54 AM, Jeff Jirsa wrote:
> > >>
>
+1
On Wed, 1 Sept 2021 at 17:37, Ekaterina Dimitrova
wrote:
> +1
>
> On Wed, 1 Sep 2021 at 12:34, Joshua McKenzie wrote:
>
> > +1
> >
> > On Wed, Sep 1, 2021 at 11:16 AM Yifan Cai wrote:
> >
> > > +1
> > >
> > >
> > > - Yifan
> > >
> > > > On Sep 1, 2021, at 7:57 AM, C. Scott Andreas
> > > wr
So to attempt to distill a set of heuristics from the discussion:
Patch release: Goal: maintain and improve stability
- Non-disruptive, non-API changing bugs are fine w/out consensus
- Bugs that change defaults or interfaces require consensus
- Improvements of any kind require consensus and must b
This looks good to me, though consensus requirements were dropped
after being noted for patch releases, was that intentional?
On Wed, Sep 1, 2021 at 12:28 PM Joshua McKenzie wrote:
>
> So to attempt to distill a set of heuristics from the discussion:
>
> Patch release: Goal: maintain and improve
Hi all,
Just to inform that now it's possible to generate CircleCI's config.yml
from the config-2_1.yml for a specific low/mid/high resource configuration
using the new -l/-m/-h flags. For example, ".circleci/generate.sh -h" will
generate a config.yml file for high resources.
This might be useful
+1 nb
Verified j8 unit tests and dtests pass
https://app.circleci.com/pipelines/github/sumanth-pasupuleti/cassandra/98/workflows/52d8cd3f-0062-407e-a3f8-f78935cff0d4
On Wed, Sep 1, 2021 at 10:23 AM Andrés de la Peña
wrote:
> +1
>
> On Wed, 1 Sept 2021 at 17:37, Ekaterina Dimitrova
> wrote:
>
>
+1
On Wed, Sep 1, 2021 at 11:55 PM Sam Tunnicliffe wrote:
> Proposing the test build of Cassandra 4.0.1 for release.
>
> sha1: 6709111ed007a54b3e42884853f89cabd38e4316
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.1-tentative
> Maven Artifacts:
> https:
> So to attempt to distill a set of heuristics from the discussion:
>
> Patch release: Goal: maintain and improve stability
> - Non-disruptive, non-API changing bugs are fine w/out consensus
> - Bugs that change defaults or interfaces require consensus
> - Improvements of any kind require consensus
Cool, moving this from dev list to JIRA, will start breaking down tasks and
document my progress there
https://issues.apache.org/jira/browse/CASSANDRA-16909
> On Aug 27, 2021, at 1:21 PM, David Capwell wrote:
>
> Push vs pull isn’t too critical, but there is one edge case to consider; if
> we
>
> I would move "Deprecating functionality" to be under Minor version.
Good call. I'll get this into a wiki article once we hash it out on thread
here.
consensus requirements were dropped after being noted for patch releases,
> was that intentional?
Hm. With how our project works we should prob
+1
On 1/9/21 21:17, Sumanth Pasupuleti wrote:
> +1 nb
>
> Verified j8 unit tests and dtests pass
> https://app.circleci.com/pipelines/github/sumanth-pasupuleti/cassandra/98/workflows/52d8cd3f-0062-407e-a3f8-f78935cff0d4
>
> On Wed, Sep 1, 2021 at 10:23 AM Andrés de la Peña
> wrote:
>
>> +1
>>
>>
+1
Dinesh
> On Sep 1, 2021, at 4:54 AM, Sam Tunnicliffe wrote:
>
> Proposing the test build of Cassandra 4.0.1 for release.
>
> sha1: 6709111ed007a54b3e42884853f89cabd38e4316
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.1-tentative
> Maven Artifacts
>
>
> There's certainly a lot of complexity in a lot of the systems here, no
> denying that, so maybe we treat the topic of API changes as "here's loose
> guidelines (destructive vs. additive w/sane defaults, etc) but plan to take
> it case-by-case" and be a bit more prescriptive on the "where do b
21 matches
Mail list logo