The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.9.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source and
+1
On 09/30/2016 02:07 PM, Jason Brown wrote:
> +1
>
> On Fri, Sep 30, 2016 at 11:53 AM, Brandon Williams wrote:
>
>> +1
>>
>> On Fri, Sep 30, 2016 at 1:51 PM, Nate McCall wrote:
>>
>>> I propose we begin the process of accepting the contribution of the
>>> dtest codebase (https://github.com/r
I propose the following artifacts for release as 2.1.16.
sha1: 87034cd05964e64c6c925597279865a40a8c152f
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.16-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1129/org/apac
On 10/07/2016 08:52 AM, Jason Brown wrote:
> +1
Jason, is this a vote for the proposed sha1: 87034cd release for 2.1.16,
or a comment to Romain? (gmail lacks some In-Reply-To/References
intelligence sometimes, so just clarifying)
> On Thu, Oct 6, 2016 at 3:45 PM, Romain Hardouin > wrote:
>
>> I'
Including myself, I count 8 +1 votes and no -1 votes for this release.
I'll get the release published!
--
Kind regards,
Michael
On 10/05/2016 06:09 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 2.1.16.
>
> sha1: 87034cd05964e64c6c925597279865a4
Nate, do think CASSANDRA-12758 should go to 2.1.x?
--
Michael
On 10/10/2016 02:26 PM, Nate McCall wrote:
> Hi Romain,
> I appreciate you speaking up about this, but I stuck with my +1 in
> order to get 2.1.16 with the NTR fix out since I have seen
> CASSANDRA-11363 with every recent client insta
and go into the next 2.1 release, or leave it for 2.2+?
--
Kind regards,
Michael
On 10/10/2016 03:09 PM, Nate McCall wrote:
>> It's too minor for a re-roll, and safe enough to just apply yourself if you
>> want it.
>
> Agreed.
>
>>
>> On Mon, Oct 10, 2016 a
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.1.16.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
I propose the following artifacts for release as 3.10.
sha1: a3828ca8b755fc98799867baf07039f7ff53be05
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1130/org/apache/c
I propose the following artifacts for release as 3.0.10.
sha1: 817ba038783212b716f6981b26c8348ffdc92f59
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1131/org/apac
I am changing my vote to -1 and closing this vote for the regression
reported in CASSANDRA-12867 by Kurt Greaves, which also affects 3.0.10.
For the record, I count 3 binding +1 votes and 3 binding -1 votes.
--
Kind regards,
Michael
On 10/31/2016 11:12 AM, Michael Shuler wrote:
> I propose
0, so help
getting that reviewed and committed would be great! I'll rebuild another
release set when that is completed.
--
Kind regards,
Michael
On 10/31/2016 10:18 AM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.10.
>
> sha1: a3828ca8b755fc9879986
On 11/04/2016 06:43 PM, Jeff Beck wrote:
> I run the local Cassandra User Group and I would love to help get the
> community more involved. I would propose holding a night to add patches to
> Cassandra some will be simple things like making sure some asserts have
> proper messages with them etc, b
+1
On 11/06/2016 11:11 PM, Jeff Jirsa wrote:
> There exists a nearly unused mailing list, client-...@cassandra.apache.org
> [0].
>
> This is a summary of the email threads over the past 12 months on that list:
>
> 1) ApacheCon Seville CFP Close notice
> 2) Datastax .NET driver question
> 3) D
If someone could set the user MichaelShuler as admin, I can help with
user requests, such as the the current request on the list to add winguzone.
--
Michael
On 11/06/2016 11:59 PM, Vladimir Yudovin wrote:
> Please add user winguzone to Wiki,
Done. Thanks!
--
Michael
I propose the following artifacts for release as 3.0.10.
sha1: 4e0bced5e6a82ebd22b074b8ef96d930c5f3159d
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1132/org/apac
I propose the following artifacts for release as 3.10.
sha1: 072b5271a88328b909b230d0e30df1c7476fdb3f
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1133/org/apache/c
>>
>> On Nov 11, 2016 2:32 AM, "Tommy Stendahl"
>> wrote:
>>
>>> +1 (non-binding)
>>>
>>>
>>> On 2016-11-08 21:08, Michael Shuler wrote:
>>>
>>>> I propose the following artifacts for release as 3.0.10.
>>>&
Thanks for all the feedback, I'm changing to a -1, too.
Vote comes to 1 binding +1, 3 binding -1, 3 non-binding -1.
--
Kind regards,
Michael
On 11/08/2016 02:09 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.10.
&
For the record, I'm changing my vote to a -1, as well.
--
Michael
On 11/11/2016 09:40 AM, Michael Shuler wrote:
> I think cassandra-3.0 HEAD is good with me, too. We can adjust the
> fixver for those that may say 3.0.11 currently.
>
We're working on configuring new donated servers for Apache Cassandra
testing in the ASF Jenkins infrastructure. I have a preference to
request INFRA set up a new git repository specifically for
build/test_run/jenkins_template scripts, separate from the main Apache
Cassandra source, but I'm wonderi
On 11/11/2016 01:02 PM, Nate McCall wrote:
>> It may also allow a
>> lower barrier for contributors interested in helping with specifically
>> build/test infrastructure.
>
> Good point for new repo.
Requested a new 'cassandra-builds' git repo! Thanks.
--
Michael
I count 3 binding +1, 1 non-binding +1, and 3 binding -1 votes. I'll
re-roll a new release, since the CASSANDRA-11039 fix has already been
committed.
--
Kind regards,
Michael
On 11/08/2016 02:08 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.0.10.
&
I propose the following artifacts for release as 3.0.10.
sha1: d6a3ef4863142c3f9fc1def911f28341fc78f2e8
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1134/org/apac
With 6 binding, 1 non-binding +1 votes and no -1 votes, this release
vote passes. I will get the artifacts published.
--
Kind regards,
Michael
On 11/11/2016 07:36 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.0.10.
>
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.10.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
I propose the following artifacts for release as 3.10.
sha1: 96d67b109a2ef858c2753bbb9853d01460cb8f8e
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1135/org/apache/c
m the
cassandra-3.11 branch.
--
Kind regards,
Michael
On 11/18/2016 12:08 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.10.
>
> sha1: 96d67b109a2ef858c2753bbb9853d01460cb8f8e
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs
Sam and I fixed up CHANGES.txt and fix versions in JIRA that had 3.11.
Since 3.10 has not been released yet,and the cassandra-3.11 branch was
created from the 3.10-tentative tag for fixed on top of 3.10, the
cassandra-3.11 branch will be used for the 3.10 release, as well as for
fixed bugs on top
ct%20%3D%20CASSANDRA%20AND%20labels%20%3D%20test-failure%20AND%20resolution%20%3D%20unresolved
--
Kind regards,
Michael Shuler
On 12/04/2016 02:07 AM, Benjamin Roth wrote:
> Sorry for jumping in so boldly before.
>
> TL;DR:
>
>- I didn't mean to delete every flaky test
l
On 11/29/2016 12:11 PM, Michael Shuler wrote:
> Sam and I fixed up CHANGES.txt and fix versions in JIRA that had 3.11.
>
> Since 3.10 has not been released yet,and the cassandra-3.11 branch was
> created from the 3.10-tentative tag for fixed on top of 3.10, the
> cassandra-3.11
Paulo pinged me on irc about getting CASSANDRA-12905 in for 3.10, so
that has been marked as release critical for 3.10 in JIRA.
--
Kind regards,
Michael
On 12/05/2016 01:26 PM, Michael Shuler wrote:
> I have again removed the 3.11 version from JIRA and corrected
> CHANGES.txt fo
(Sent to private@ a couple weeks ago)
We are currently working on configuring newly donated ASF recommended
compute resources to the ASF Jenkins environment and will be
transferring unit and dtests over there once the infrastructure is
running jobs successfully.
We are receiving requests for new
ets I linked were just an example of my experience for you, the
community, to follow. Please, do coordinate on dev@ here, if there's a
desire to help, but I won't be adding servers to our account for you -
you do that :)
--
Kind regards,
Michael
On 12/06/2016 09:47 AM, Michael Shuler
The current branch merge path is, in full:
cassandra-2.1
|
cassandra-2.2
|
cassandra-3.0
|
cassandra-3.11
|
cassandra-3.X
|
trunk
Wherever you start, please follow through the complete path to trunk.
I reopened JIRAs #12768, #12817, and #12694 for skipping cassandra
- All of the unit test variations passed 100% on commit 01cb787.
- CASSANDRA-13056 set as blocker for 3.10 release, if we're pushing for
100% dtest passing. This test is also failing in 3.X and trunk.
- A couple other dtest tests appear to flake on multiple runs on the
cassandra-3.11 branch. Anothe
(CASSANDRA-13056 test fix was committed and jobs re-run.)
Current release blockers in JIRA on the cassandra-3.11 branch are:
https://issues.apache.org/jira/browse/CASSANDRA-12617
https://issues.apache.org/jira/browse/CASSANDRA-13058
--
Kind regards,
Michael
Added you as a contributor and assigned.
--
Michael
On 12/23/2016 09:55 AM, Prakash Chauhan wrote:
> Hi All,
>
> I have recently created a JIRA ticket
> https://issues.apache.org/jira/browse/CASSANDRA-12968 . Unfortunately I am
> not getting any option to assign it to myself.
> Can someone
On 12/20/2016 03:48 PM, Michael Shuler wrote:
> Current release blockers in JIRA on the cassandra-3.11 branch are:
>
> https://issues.apache.org/jira/browse/CASSANDRA-12617
> https://issues.apache.org/jira/browse/CASSANDRA-13058
and https://issues.apache.org/jira/browse/CAS
Thanks! I think I was looking at a wrong JIRA, sorry 'bout that.
--
Michael
On 01/04/2017 12:31 PM, Oleksandr Petrov wrote:
> #13025 was updated yesterday. It just needs some feedback, but we know what
> the problem is there.
>
> On Wed, Jan 4, 2017 at 5:32 PM Michael Shuler
Latest cassandra-3.11_dtest run failed on one test,
system_auth_ks_is_alterable_test:
https://issues.apache.org/jira/browse/CASSANDRA-13113
The dtest variations (novnode, offheap, upgrade, large) have other
failures, but if the green light for release is unit tests and the
default dtest, we're cl
Generally, fixver has only been set during commits - I only marked 3.10
and blocker status to highlight the few that failed votes, in order to
sort of cheerlead "fix me so we can release!" JIRA tickets. The full
test-failure list is probably the more "realistic" view, since any of
those may occur.
I had the same thought. 3.10 is the tick, so a 3.11 bugfix tock follows
the intended final fix release for closing out tick-tock. Throwing a
3.10.1 out there would add more user confusion and would be the exact
same contents as a 3.11 release versioned package set anyway.
--
Michael
On 01/10/201
+1 to freeze with this clarified branch situation.
--
Michael
On 01/13/2017 11:53 AM, Aleksey Yeschenko wrote:
> To elaborate further, under the current consensus there would be no 3.12
> release.
>
> Meaning that there are a few features that already made it to 3.X (3.12) that
> would
> eith
://cassci.datastax.com/job/cassandra-3.11_utest_compression/23/
https://cassci.datastax.com/job/cassandra-3.11_dtest/31/
--
Kind regards,
Michael Shuler
signature.asc
Description: OpenPGP digital signature
try again.
--
Kind regards,
Michael
On 01/13/2017 06:46 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.10.
>
> sha1: 9c2ab25556fad06a6a4d58f4bb652719a8a1bc27
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/
Thanks, Sylvain!
--
Michael
On 01/27/2017 02:33 AM, Sylvain Lebresne wrote:
> Fyi, I just committed CASSANDRA-13025 so it's ready for a re-roll as far as
> I can tell.
>
> On Tue, Jan 24, 2017 at 12:31 AM, Michael Shuler
> wrote:
>
>> This vote is being failed f
I propose the following artifacts for release as 3.10.
sha1: 3cf415279c171fe20802ad90f181eed7da04c58d
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1137/org/apache/c
With 5 binding +1, 1 non-binding +1, and no -1 votes, this 3.10 vote has
passed. I'll get the artifacts published and an announcement out!
--
Kind regards,
Michael
P.S.: woot!
On 01/31/2017 03:29 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.10.
&
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.10.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source and
Thank you for working on this, Ay, I appreciate it.
--
Michael
On 02/05/2017 11:56 AM, Aleksey Yeschenko wrote:
> A handy filter to see if you’ve got any JIRAs as assignee/reviewer
> that need correction:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20Cassandra%20and%20fixVersio
On 02/07/2017 03:23 AM, Aleksandr Sorokoumov wrote:
> Hello,
>
> I have been checking out recently some of the dtest-related issues and wanted
> to share an idea. It might be useful to see dtest’s commit id in the Jenkins
> logs. AFAIK Jenkins clones dtest master right now.
> For example, it wou
(sorry for previous blank reply..)
Please create a JIRA and it can be assigned to me. `mshuler` is my JIRA
user.
--
Kind regards,
Michael
On 02/07/2017 03:23 AM, Aleksandr Sorokoumov wrote:
> Hello,
>
> I have been checking out recently some of the dtest-related issues
> and wanted to share an
/ztSHQJ
[2]: (NEWS.txt) https://goo.gl/nrengr
--
Kind regards,
Michael Shuler
signature.asc
Description: OpenPGP digital signature
/AYblr5
[2]: (NEWS.txt) https://goo.gl/gIXxgR
--
Kind regards,
Michael Shuler
signature.asc
Description: OpenPGP digital signature
/17RivH
[2]: (NEWS.txt) https://goo.gl/axKXys
--
Kind regards,
Michael Shuler
signature.asc
Description: OpenPGP digital signature
Vote result:
8 +1 binding votes
1 +1 non-binding votes
0 +0 or -1 votes
This release vote passed, so I'll get the artifacts published.
--
Kind regards,
Michael
On 02/15/2017 07:16 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 2.1.17.
&
Vote result:
8 +1 binding votes
2 +1 non-binding votes
0 +0 or -1 votes
This release vote passed, so I'll get the artifacts published.
--
Kind regards,
Michael
On 02/15/2017 07:16 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 2.2.9.
&
Vote result:
8 +1 binding votes
1 +1 non-binding votes
0 +0 or -1 votes
This release vote passed, so I'll get the artifacts published.
--
Kind regards,
Michael
On 02/15/2017 07:15 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.0.11.
&
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.11.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.1.17.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.9.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source an
>
>>http://dl.bintray.com/apache/cassandra/pool/main/c/cassandra/ <
>> http://dl.bintray.com/apache/cassandra/pool/main/c/cassandra/>
>>
>> But it requires to manually download and put them back to the apt cache.
>>
>> It is quite handy for point r
I propose the following artifacts for release as 3.0.12.
This release addresses a possible 2.1->3.0 upgrade issue[3], along with
a few fixes committed since 3.0.11.
sha1: 50560aaf0f2d395271ade59ba9b900a84cae70f1
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.
On 03/07/2017 10:15 AM, Michael Shuler wrote:
> The vote will be open for 72 hours (longer if needed).
I'd like to amend this vote to be 48 hours, if there are no complaints
with this timeframe.
--
Kind regards,
Michael
signature.asc
Description: OpenPGP digital signature
With 7 binding and 2 non-binding +1 votes, the release of 3.0.12 has
passed. I'll get the artifacts uploaded first thing in the morning,
since it's a bit late tonight.
--
Warm regards,
Michael
On 03/07/2017 10:15 AM, Michael Shuler wrote:
> I propose the following artifacts f
) https://goo.gl/sc8BvB
[2]: (NEWS.txt) https://goo.gl/S5gpKA
[3]: https://issues.apache.org/jira/browse/CASSANDRA
--
Warm regards,
Michael Shuler
signature.asc
Description: OpenPGP digital signature
+1
On 03/20/2017 05:32 PM, Jeff Jirsa wrote:
> There's no reason for the dev list to get spammed everytime there's a
> github PR. We know most of the time we prefer JIRAs for real code PRs, but
> with docs being in tree and low barrier to entry, we may want to accept
> docs through PRs ( see https
On 03/22/2017 12:41 PM, François Deliège wrote:
> A first actionable step is to increase the visibility of the test
> coverage. Ideally this would be integrated in the Jenkins run on
> Apache. Michael Shuler, is this something you can take a look at?
> Let me know if we can help.
I won't reply to the obvious spam to hilight it any further, so new
message..
Could the mailing list moderator that approved the "client list" message
identify themselves and possibly explain how that was seen as a valid
message about the development of Apache Cassandra?
--
Kind regards,
Michael
No replies, please.
This was resolved privately and was a simple mistake.
--
Kind regards,
Michael
+1
On 03/29/2017 08:21 AM, Jason Brown wrote:
> Hey all,
>
> Following up my thread from a week or two ago (
> https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassandra.apache.org%3E),
> I'd like to propose a vote to change to allow any potenti
I propose the following artifacts for release as 3.0.13.
sha1: 91661ec296c6d089e3238e1a72f3861c449326aa
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.13-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1142/org/apac
On 04/12/2017 12:10 AM, mck wrote:
>
> On 10 March 2017 at 05:51, Jason Brown wrote:
>> A nice convention we've stumbled into wrt to patches submitted via Jira is
>> to post the results of unit test and dtest runs to the ticket (to show the
>> patch doesn't break things).
>> [snip]
>> As an exam
Just a quick update after tests all finished on this 3.0.13-tentative
tag sha. One dtest failed on the standard and "novnode" jobs, which we
have an existing JIRA for, CASSANDRA-13113. All the other test runs
completed successfully.
http://12.am/tmp/3.0.13-tentative-results.png
--
Kind regards,
This 3.0.13 release vote passes with 7 binding +1, 1 non-binding +1, and
no other votes.
Thanks for the input! I'll get the artifacts rolled out.
--
Kind regards,
Michael
On 04/11/2017 01:59 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.0.13.
&
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.13.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
On 04/25/2017 09:56 AM, Eric Evans wrote:
> On Tue, Apr 25, 2017 at 2:56 AM, Alain RODRIGUEZ wrote:
>> Should / could we have INFRA automatically unsubscribing people sending
>> those messages? I believe this would be the best solution, as more people
>> mentioned a year ago. I would like at least
On 04/25/2017 12:52 PM, Mark Thomas wrote:
> On 25/04/17 16:11, Michael Shuler wrote:
>> Many lists include a footer that have unsub info - does ezmlm support
>> footer append? I wouldn't mind it, if it helps users, and it seems
>> simpler than trying to filter random
On 04/26/2017 07:51 AM, Nate McCall wrote:
> I'm fine with that footer. I see that from other lists I'm on and it
> doesn't bother me.
https://issues.apache.org/jira/browse/INFRA-14017 request made.
--
Michael
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%203.11.x
Currently 374 tickets - this is the list we're talking about. Anything
that's not a bug fix intended for the cassandra-3.11 branch should
probably be moved to trunk/4.0.
--
Kind regards,
Michae
On 04/30/2017 05:29 PM, mck wrote:
>
> Narrowing down the list to only
> - types: Feature, Improvements, Task, Wish, Sub-task,
> - versions: 3.11.0 and 3.11.x, and
> - status: Opened, In Progress, Reopened
>
> there's 235 issues.
>
> https://issues.apache.org/jira/browse/CASSANDRA-13481?jql
I propose the following artifacts for release as 3.0.14.
sha1: f3e38cb638113c2a23855a104d6082da5bc10ddb
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.14-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1143/org/apac
I propose the following artifacts for release as 3.11.0.
sha1: 88dee7e9d515ad94ecf8f2309f1e6138ec79e1a2
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.0-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1145/org/apac
Sounds good to me - I'll work up a 2.2.10 artifact set tomorrow.
Looking at our current branches and the EOL TBD dates on the download
page, I believe the 4.0 references for sunsetting branches was prior to
considering a 3.11.0 release with ongoing support for the branch.
Should we also do a 2.1.
l cost to having it open, and if a real critical bug
> pops up between now and 4.0, the hundreds/thousands of people running
> 2.1 in prod will appreciate a fix.
>
> - Jeff
>
>
>
> On Tue, Jun 20, 2017 at 8:20 PM, Michael Shuler <mailto:mich...@pbandjelly.org>> w
I propose the following artifacts for release as 2.1.18.
sha1: 9369db1dfd92d4eb76284cfb68b1ffb9d22c9b06
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.18-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1146/org/apac
I propose the following artifacts for release as 2.2.10.
sha1: 83f28ce3c4eeff75ce70855a56b6155047ce8e9a
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1147/org/apac
With 6 binding +1 votes, 2 non-binding +1, and no other votes, this
release vote has passed.
--
Kind regards,
Michael
On 06/19/2017 03:37 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.0.14.
>
> sha1: f3e38cb638113c2a23855a104d6082da5bc10ddb
> Git:
With 5 binding +1 votes, 1 non-binding +1, and no other votes, this
release vote has passed.
--
Kind regards,
Michael
On 06/19/2017 06:10 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.11.0.
>
> sha1: 88dee7e9d515ad94ecf8f2309f1e6138ec79e1a2
> Git:
(resend with subject +PASSED)
With 5 binding +1 votes, 1 non-binding +1, and no other votes, this
release vote has passed.
--
Kind regards,
Michael
On 06/19/2017 06:10 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.11.0.
>
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.11.0.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.14.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
With 3 binding +1 votes and no other votes, this 2.1.18 vote has passed.
--
Kind regards,
Michael
On 06/21/2017 03:18 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 2.1.18.
>
> sha1: 9369db1dfd92d4eb76284cfb68b1ffb9d22c9b06
> Git:
> http://git-wi
With 5 binding +1 votes and no other votes cast, this release vote has
passed.
--
Kind regards,
Michael
On 06/21/2017 03:20 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 2.2.10.
>
> sha1: 83f28ce3c4eeff75ce70855a56b6155047ce8e9a
> Git:
>
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.1.18.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.10.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
Standard unix/linux systems policy is that editable configurable files
go under /etc. It is not proper to edit files under /{s}bin or
/usr/{s}bin. $PATH contains /{s}bin and /usr/{s}bin files as executables
that can be run by a user, so that's why the basic separation of the
runnable files and tuna
Just a quick FYI - builds.apache.org has a scheduled maintenance window
this weekend for a server migration and software upgrades.
https://lists.apache.org/thread.html/1185e30193ff764870e9a7f58818e0d6a9af3a50b6e3ebd62476244c@%3Cbuilds.apache.org%3E
--
Kind regards,
Michael
-
201 - 300 of 407 matches
Mail list logo
