I propose the following artifacts for release as 3.0.19.
sha1: a81bfd6b7db3a373430b3c4e8f4e930b199796f0
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.19-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1183/org/apac
This vote passed with 8 binding +1, 2 non-binding +1, and no other votes.
Kind regards,
Michael Shuler
On 10/24/19 12:25 PM, Michael Shuler wrote:
I propose the following artifacts for release as 2.2.15.
sha1: 4ee4ceea28a1cb77b283c7ce0135340ddff02086
Git:
https://gitbox.apache.org/repos/asf
This vote passed with 8 binding +1, 3 non-binding +1, and no other votes.
Kind regards,
Michael Shuler
On 10/24/19 12:25 PM, Michael Shuler wrote:
I propose the following artifacts for release as 3.0.19.
sha1: a81bfd6b7db3a373430b3c4e8f4e930b199796f0
Git:
https://gitbox.apache.org/repos/asf
This vote passed with 7 binding +1, 2 non-binding +1, and no other votes.
Kind regards,
Michael Shuler
On 10/24/19 12:26 PM, Michael Shuler wrote:
I propose the following artifacts for release as 3.11.5.
sha1: b697af87f8e1b20d22948390d516dba1fbb9eee7
Git:
https://gitbox.apache.org/repos/asf
This vote passed with 6 binding +1, 3 non-binding +1, and no other votes.
Kind regards,
Michael Shuler
On 10/24/19 12:26 PM, Michael Shuler wrote:
I propose the following artifacts for release as 4.0-alpha2.
sha1: ca928a49c68186bdcd57dea8b10c30991c6a3c55
Git:
https://gitbox.apache.org/repos
site should be published. I can take care of it
tomorrow.
Reference:
https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite
On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler
wrot
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.19.
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 sou
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.11.5.
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 sou
The Cassandra team is pleased to announce the release of Apache
Cassandra version 4.0-alpha2.
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
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.15.
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 sou
remember how this was handled? Am I missing something
obvious?
Jon
On Tue, Oct 29, 2019 at 1:28 PM Jon Haddad wrote:
I'll take a look at the website generation. Thanks for fixing manually
for now.
On Tue, Oct 29, 2019 at 1:16 PM Michael Shuler
wrote:
I have updated the new releases
+1
Scott, was your NGCC talk videoed and uploaded anywhere? I would love to
watch, since I missed the event.
Kind regards,
Michael
On 11/1/19 9:07 AM, Scott Andreas wrote:
+1 nb
On Nov 1, 2019, at 5:36 AM, Benedict Elliott Smith wrote:
+1
On 01/11/2019, 12:33, "Mick Semb Wever" wrote
-1 (I looked into this when we released 4.0-alpha1)
"During the process of developing software and preparing a release,
various packages are made available to the developer community for
testing purposes. Do not include any links on the project website that
might encourage non-developers to do
/19 2:06 PM, Michael Shuler wrote:
-1 (I looked into this when we released 4.0-alpha1)
"During the process of developing software and preparing a release,
various packages are made available to the developer community for
testing purposes. Do not include any links on the project website t
e without crossing that line into
risking people running alpha code on accident in a production environment.
On Mon, Nov 4, 2019 at 3:10 PM Michael Shuler
wrote:
I will also add that I did send the user@ list 4.0-alpha release notes,
along with dev@, and also added to the @cassandra tweet last week.
On 1/11/20 4:48 AM, Mick Semb Wever wrote:
This brings up the issue that links to builds on tickets should ideally refer
to information that is permanent.
This could be done by configuring builds to keep status and logs but not the
built artefacts (and/or adding bigger disks). I will now up
On 1/11/20 9:17 AM, Michael Shuler wrote:
On 1/11/20 4:48 AM, Mick Semb Wever wrote:
This brings up the issue that links to builds on tickets should
ideally refer to information that is permanent.
This could be done by configuring builds to keep status and logs but
not the built
On 1/11/20 10:02 AM, Mick Semb Wever wrote:
This brings up the issue that links to builds on tickets should
ideally refer to information that is permanent. This could be
done by configuring builds to keep status and logs but not the
built artefacts (and/or adding bigger disks). I will now up
On 1/23/20 12:44 PM, mck wrote:
ASF policy is that patches from contributors that haven't a ICLA
filed can not have their patches automatically run through any ASF CI
system. It's up to a committer (or someone who has filed a ICLA) to
trigger the test run on the patch.
I couldn't find this CI+
On 1/23/20 2:13 PM, Mick Semb Wever wrote:
ASF policy is that patches from contributors that haven't a ICLA
filed can not have their patches automatically run through any ASF CI
system. It's up to a committer (or someone who has filed a ICLA) to
trigger the test run on the patch.
I couldn't f
On 1/23/20 3:53 PM, David Capwell wrote:
2) Nightly build email to dev@?
Nope. builds@c.a.o is where these go.
https://lists.apache.org/list.html?bui...@cassandra.apache.org
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@
On 1/31/20 9:58 AM, Dimitar Dimitrov wrote:
one corollary of the way the algorithm works (or more
precisely might not work) with multiple seeds or simultaneous
multi-node bootstraps or decommissions, is that a lot of dtests
start failing due to deterministic token conflicts. I wasn't
able to fix
pg: Signature made Thu 30 Jan 2020 12:27:19 PM CST
gpg:using RSA key A4C465FEA0C552561A392A61E91335D77E3E87CB
gpg: Can't check signature: No public key
Validation FAILED!!
# lgtm (I have not `apt-key add`ed key..)
mshuler@hana:~/tmp/cassandra-4.0-alpha3$ egrep 'Date:|Changed-By:'
Only have a moment to respond, but Mick hit the higlights with
containerization, parallelization, these help solve cleanup, speed, and
cascading failures. Dynamic disposable slaves would be icing on that
cake, which may require a dedicated master.
One more note on jobs, or more correctly unnec
On 2/3/20 5:21 PM, Mick Semb Wever wrote:
Summary of notes:
- Artifact set checks out OK with regards to key sigs and checksums.
- CASSANDRA-14962 is an issue when not using the current deb build
method (using new docker method results in different source artifact
creation & use). The docker rp
On 2/4/20 3:59 PM, Mick Semb Wever wrote:
Proposing the test build of Cassandra 4.0-alpha3 for release.
sha1: 5f7c88601c65cdf14ee68387ed68203f2603fc29
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha3-tentative
Maven Artifacts:
https://repository.apac
I like this idea for keeping binary deployment size down. I'm not sure
how to handle it for the tarballs, but we could certainly split the docs
out of the debian and rpm packages to add
cassandra-docs_.{deb,rpm} packages, so they are installable
separately, if the user wants them. This is commo
This is great, thanks, the project appreciates the effort. 2019 is over,
don't worry about the past. Moving forward in little or large steps is
the goal. :)
If you didn't get a chance to attend the first Contributor Meeting,
there will be more. Patrick sent out a survey last week for feedback,
+1
On 2/11/20 2:36 AM, Mick Semb Wever wrote:
Proposing the test build of Cassandra 3.0.20 for release.
sha1: 89edf5073ba4181dd2f70294cdbcb47f5a45c82e
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.20-tentative
Maven Artifacts:
https://repository.apache.o
+1
On 2/10/20 2:31 PM, Mick Semb Wever wrote:
Proposing the test build of Cassandra 2.2.16 for release.
sha1: c4d9e9ca4ade40b956e37935bce68737b0c063b9
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.16-tentative
Maven Artifacts:
https://repository.apache.o
+1
On 2/11/20 2:38 AM, Mick Semb Wever wrote:
Proposing the test build of Cassandra 3.11.6 for release.
sha1: cb779ab9a631c13a245926f55320392c4468c6f0
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.6-tentative
Maven Artifacts:
https://repository.apache.o
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.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 sou
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.20.
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 sou
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.11.6.
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 sou
On 3/3/20 12:16 AM, Mick Semb Wever wrote:
I'm happy to cut a release later this week or next, once these and
others yet to be mentioned get merged. We need to do another round on
the release process to wrap up CASSANDRA-14970.
Great! I have a little availability over the next week or two, onc
On 3/18/20 11:15 AM, Ekaterina Dimitrova wrote:
Hello everyone,
I am interested to help with "CASSANDRA-15586 4.0 quality testing: Cluster
Setup and Maintenance"
Awesome!
There was a short discussion last night on Slack but I know that not
everyone keeps an eye on those chats so I decided to
+1
Code link is actually a branch at:
https://github.com/apache/cassandra-in-jvm-dtest-api/tree/CASSANDRA-15539
Just curious why master isn't the active dev branch, since there's
nothing but a license and blank readme there. No biggie, just had to go
look for it when I followed the link.
Mic
updated vote: -1
Thanks for the run through, Mick.
On 3/20/20 12:01 PM, Michael Shuler wrote:
+1
Code link is actually a branch at:
https://github.com/apache/cassandra-in-jvm-dtest-api/tree/CASSANDRA-15539
Just curious why master isn't the active dev branch, since there's
not
We did something similar on CassCI for the dev branch jobs and skipped
branch names that contained 'nobuild'.
jobs:
build:
branches:
ignore:
- /.*nobuild.*/
..would be the equivalent?
Michael
On 3/24/20 4:08 PM, David Capwell wrote:
It looks like you can configure at the
It has been a few years, but I think we came to basically the same
conclusion on build/test skipping in autojobs for CassCI. Most wanted
the job runs all the time, but a few wanted to skip runs for scratch or
WIP branches, in order to preserve resources when they didn't care what
the result was
+1
On 4/10/20 6:02 PM, Mick Semb Wever wrote:
Proposing the test build of Cassandra 4.0-alpha4 for release.
sha1: d00c004cc10986fc41c2070f9c5d0007e03a45c3
Git:
https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha4-tentative
Maven Artifacts:
https://repository.ap
I updated the severity and complexity of this ticket. It is not a
trivial fix, but I agree that as time goes on, this is becoming higher
priority to focus some effort on it.
(fyi, I'm not volunteering, is way beyond my means :) )
Kind regards,
Michael
On 6/10/20 11:55 PM, manish khandelwal wr
non-binding +1
--
Michael
On 04/27/2015 09:46 AM, Jake Luciani wrote:
I propose the following artifacts for release as 2.1.5.
sha1: 3c0a337ebc90b0d99349d0aa152c92b5b3494d8c
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.5-tentative
Artifacts:
https://r
On 06/10/2015 07:20 AM, Amit Singh F wrote:
Could anybody please provide any possible solution for this or some pointers to
get it done.
Run tests on the cassandra-2.0 branch HEAD.
Feel free to discuss issues when running on the latest branch commit.
There have been lots of test problems sol
+1 non-binding
On 06/05/2015 10:27 AM, Jake Luciani wrote:
I propose the following artifacts for release as 2.2.0-rc1.
sha1: b0ae285bdc7377a64ed92f01c67ff46b40ecaac0
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.0-rc1-tentative
Artifacts:
https://reposit
+1 non-binding
On 06/19/2015 07:56 AM, Jake Luciani wrote:
I propose the following artifacts for release as 2.0.16.
sha1: 23e66a9d1c50e4331e8c1d212c2eeb940c5471fa
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.16-tentative
Artifacts:
https://repository.ap
+1 non-binding
On 06/19/2015 07:59 AM, Jake Luciani wrote:
I propose the following artifacts for release as 2.1.7.
sha1: 718c144324d170535d4f1a1e79dd9869cce19ed1
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.7-tentative
Artifacts:
https://repository.apac
Michael would like to recall message [VOTE].. :)
On 06/22/2015 10:12 AM, Michael Shuler wrote:
+1 non-binding
+1 non-binding
On 07/06/2015 01:47 PM, Jake Luciani wrote:
I propose the following artifacts for release as 2.2.0-rc2.
sha1: ebc50d783505854f04f183297ad3009b9095b07e
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.0-rc2-tentative
Artifacts:
https://reposit
+1 non-binding
On 07/06/2015 12:04 PM, Jake Luciani wrote:
I propose the following artifacts for release as 2.1.8.
sha1: db39257c34152f6ccf8d53784cea580dbfe1edad
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.8-tentative
Artifacts:
https://repository.apac
When we set up autojobs for the dev branches, I did some digging around
the jenkins / githubPR integration, similar to what spark is doing. I'd
be completely on board with working through that setup, if it helps this
workflow.
Michael
On 07/08/2015 03:02 PM, Carl Yeksigian wrote:
Spark has b
+1 (non-binding)
On 07/31/2015 08:42 AM, Jake Luciani wrote:
I propose the following artifacts for release as 3.0.0-alpha1.
sha1: b090ed6938c0fad792e51757384bd5ac7f35a301
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-alpha1-tentative
Artifacts:
https:/
Hi Devs,
I migrated Jenkins to a larger server and most everything looks right,
except autojobs. The first runs of autojobs started a build of every
developer's jobs - it queued ~1700 jobs which would have resulted in
launching roughly 9000 AWS instances. Needless to say, autojobs has been
di
After some tedious bogus job cleanup, Jenkins is now processing the
backlog of jobs normally, and new branches will get picked up as
autojobs gets its runs in. Users of the post-commit hook will get jobs
queued normally, as well. Hang in there as the queue gets worked through
and thanks for you
This is a prompt for Cassandra developers to discuss the alternatives
and let Test Engineering know what you desire.
As discussed a few times in person, on irc, etc., there are a couple
different ways we can run tests in Jenkins, particularly
cassandra-dtest. The Cassandra developers are the c
+1 non-binding
Commit that CR to cassandra-2.0 branch HEAD, leaving the tag where it is
and I can build DSC with it included :)
--
Michael
On 09/17/2015 08:48 AM, Jake Luciani wrote:
I'm not inclined to re-roll for a missing CR but if others feel strongly
about it I will do it.
On Wed, Sep
non-binding +1
On 09/18/2015 07:47 AM, Jake Luciani wrote:
I propose the following artifacts for release as 2.0.17.
sha1: c4de752758c3cf7f5de5a92e4ede30e430a36255
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.17-tentative
Artifacts:
https://repository.ap
non-binding +1
On 09/19/2015 01:42 PM, Jake Luciani wrote:
I propose the following artifacts for release as 3.0.0-rc1.
sha1: c95a7098cf77b5b8e96feb7c39aca8fec3a02f9c
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-rc1-tentative
Artifacts:
https://reposit
non-binding +1
--
Michael
On 11/06/2015 03:34 PM, Jake Luciani wrote:
I propose the following artifacts for release as 3.0.0.
sha1: 96f407bce56b98cd824d18e32ee012dbb99a0286
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.0-tentative
Artifacts:
https://rep
On 11/25/2015 07:36 PM, Michael Edge wrote:
> I'd like to update the read/write path description on the wiki (see link
> below) by adding a couple of UML sequence diagrams I drew a while ago. I
> think they are much better than long textual descriptions for describing
> the order of operations on c
This mailing list is for discussing the development of Apache Cassandra.
Either talk to your support folks at DataStax or try the user@ list for
help installing (which is probably also inappropriate for DSE).
FWIW, this is a simple user issue with multiple versions of the same
software in apt repo
On 04/11/2016 12:42 PM, Anuj Wadehra wrote:
> Can someone help me with this one?
This is the type of question you should ask the user@ list. The dev@
list is specifically for the development *of* Cassandra.
> What should be a resonable criteria for taking 3.x releases in
> production?
Short answ
On 06/20/2016 01:16 PM, Will Hayworth wrote:
> Hey all--I didn't want to add more heat than light to this, but I think at
> this point I'm behooved to speak up. :) I'm a developer at Atlassian (the
> folks who make JIRA); I don't work on JIRA itself but have some familiarity
> with its mechanics an
On 06/26/2016 11:03 AM, Jonathan Ellis wrote:
>
> Is Snap a new packaging format like deb/rpm, or does it consume the
> existing deb package?
It's an LXD container delivery system.
--
Kind regards,
Michael
On 06/27/2016 09:59 AM, Jonathan Ellis wrote:
> How would I deploy a cluster with Snap?
>
> With the package I can pre-deploy my configuration to the node with cluster
> name, seeds, etc. With Snap do I have to build a custom container to do
> that? Or is there some way to pull in config from th
On 07/11/2016 02:40 AM, Vlad wrote:
>
> I see 3.0.8 tag (8b21d9) at
> https://git1-us-west.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/cassandra-3.0.8
> but not on https://github.com/apache/cassandra/commits/cassandra-3.0
Tag mirroring to github is sometimes a little slow, but it
I propose the following artifacts for release as 3.8.
sha1: c3ded0551f538f7845602b27d53240cd8129265c
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1123/org/apache/cas
Thanks for the clarity, Jonathan. I agree that an August 3.8 release
target sounds like the most reasonable option, at this point in time.
With Sylvain's binding -1, this vote has failed.
--
Kind regards,
Michael Shuler
On 07/21/2016 05:33 PM, Jonathan Ellis wrote:
> I feel like the
pgrade *and* the fact the vast majority of our
> upgrade tests are failing is not _obviously_ enough to hold a
> release, without the need for further considerations. This speaks imo
> poorly of the PMC attachment to release quality.
>
> But you are correct on the technicality of vote
; a lot more preferable than failing the schedule for 4 upcoming 3.x and
>>> 3.0.x releases.
>>>
>>> 3.9, after all, *does* have a month of bugfix only stabilisation changes
>>> in it. So does 3.0.9. The sooner we can get those into people’s hands,
>>
On 08/03/2016 03:31 PM, Kant Kodali wrote:
> when are we moving from SEDA to TPC? any timeline or something that I can
> look out for?
>
You could follow the JIRA ticket parent and children, review patches,
etc. :) https://issues.apache.org/jira/browse/CASSANDRA-10989
--
Kind regards,
Michael
On 08/15/2016 01:12 PM, Chris Mattmann wrote:
> How is it harder to point someone to mail?
Mailing lists can be simple to join and converse. Like some other folks,
I'm on a large number of lists and get massive amounts of mail.
Extremely busy mailing lists need user-level care for them to be
funct
Yesterday, it was suggested on #cassandra-dev that when 3.9 is ready for
release, we release 3.8 with the same code base. My plan is to force
push the contents of cassandra-3.9 branch to the cassandra-3.8 branch,
updating the version appropriately, so we can build/test from the 3.8
branch, as usual
On 08/16/2016 10:52 AM, Aleksey Yeschenko wrote:
> No objections, the plan sounds good to me.
>
> In addition to that, prep for pushing 3.0.9 out with 3.9.
Thanks. Yes, 3.0.9 is also up for release, without any branch song and
dance :)
--
Michael
It looks like Dave replied to your first email that he added your wiki
user to be able to edit pages. Did your login not work properly, or did
you get some sort of error editing the wiki?
(cc'ed directly, too)
--
Kind regards,
Michael
On 08/18/2016 08:15 AM, Danielle Blake wrote:
> Hi,
>
> I e
Jenkins jobs in ABORTED status are bad. A lot of times they tend to be
ignored/re-run to get completed results, which is OK, only if the reason
is due to server setup or configuration problems. There's a relatively
recent pattern of o.a.c.cql3.validation test hanging up jobs, and I've
been unable t
Another couple ABORT examples have presented themselves, tonight, one
that has logs.
Usually we'll see unit tests finish similar to:
01:57:39 [junit] Testsuite:
org.apache.cassandra.cql3.statements.PropertyDefinitionsTest
01:57:39 [junit] Testsuite:
org.apache.cassandra.cql3.statements.Pr
On 09/02/2016 05:19 AM, Andy Cobley wrote:
> However I’ve just tried apache-cassandra-3.10-SNAPSHOT and am
> still getting
>
> "Cassandra 3.0 and later require Java 8u40 or later.”
What is the git sha of your 3.10-SNAPSHOT build?
I see this was committed to trunk Jul 27, so perhaps your build i
I have an ongoing INFRA ticket with the testing issues we've seen when
utilizing the ASF's Jenkins infrastructure. Basically, the results are
erratic, due to other project (and Cassandra) concurrent test runs. Our
testing on CassCI is pretty stable, since we do not run any concurrent
tests. Cassand
On 09/09/2016 02:31 PM, Jeff Jirsa wrote:
> Can you describe the size and number of slaves we need to do things "right"?
>
> How many cores? How much ram? How many slaves?
We currently run all unit test jobs on m3.xlarge instances, which seems
to work fine. (Almost all the dtest jobs run OK on m3
What's preventing the use of the 3.6 or 3.7 releases where this bug is
already fixed? This is also fixed in the 3.0.6/7/8 releases.
Michael
On 09/14/2016 08:30 PM, Jonathan Haddad wrote:
> Unfortunately CASSANDRA-11618 was fixed in 3.6 but was not back ported to
> 3.5 as well, and it makes Cassan
non-binding +1
Here's the testing summary on the 3.0.9-tentative tag:
http://12.am/tmp/3.0.9-tests.png
--
Michael
On 09/15/2016 01:57 PM, Jake Luciani wrote:
> I propose the following artifacts for release as 3.0.9.
>
> sha1: d600f51ee1a3eb7b30ce3c409129567b70c22012
> Git:
> http://git-wip-
The cassandra-3.9 branch HEAD, commit bb371ea, looks good to release
(which will also be released as 3.8, changing just the version number).
I'm re-running a couple jobs right now, but overall, I think we hit the
goal of a clean board: http://cassci.datastax.com/view/cassandra-3.9/
If there are n
The cassandra-2.2 branch looks stable, has a lot of bug fixes, and Tyler
had someone ask about a 2.2.8 release. Any objections to rolling this up
for a vote? http://cassci.datastax.com/view/cassandra-2.2/
--
Kind regards,
Michael
I propose the following artifacts for release as 2.2.8.
sha1: e9fe96f404b6a936ac5dbceb8f3934fe0d098a97
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.8-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1125/org/apache
There were no immediate objections and I didn't spot any in-progress
tickets for 2.2.8, so go vote!
--
Michael
wo separate votes works.
>
> --
> AY
>
> On 23 September 2016 at 12:36:54, Michael Shuler (mich...@pbandjelly.org)
> wrote:
>
> The cassandra-3.9 branch HEAD, commit bb371ea, looks good to release
> (which will also be released as 3.8, changing just the version num
bug fix release a month
> later. This breaks that promise.
>
> On Fri, Sep 23, 2016 at 4:23 PM Michael Shuler
> wrote:
>
>> Thanks! I'll do these release builds and start votes, first thing
>> Monday morning, unless I find some time on Sunday.
>>
>> --
here is consensus among PMCs. If something changed, it’ll be
> reflected in the vote.
>
> -- AY
>
> On 23 September 2016 at 21:39:09, Michael Shuler
> (mich...@pbandjelly.org) wrote:
>
> Jonathan's is a pretty compelling perspective.
>
> -- Michael
>
> On 09
I propose the following artifacts for release as 3.8.
sha1: ce609d19fd130e16184d9e6d37ffee4a1ebad607
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.8-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1126/org/apache/cas
[2]: (NEWS.txt) https://goo.gl/1w6Ec1
--
Kind regards,
Michael Shuler
Jon, is there a JIRA ticket for this request? I appreciate everyone's
input, and I think this is a fine proposal.
--
Kind regards,
Michael
On 09/14/2016 08:30 PM, Jonathan Haddad wrote:
> Unfortunately CASSANDRA-11618 was fixed in 3.6 but was not back ported to
> 3.5 as well, and it makes Cassan
I foresee many arithmetic errors with 3.X.. :)
--
Michael
On 09/27/2016 05:18 AM, Sylvain Lebresne wrote:
> We have a number of tickets that we now have to wait on 4.0 due to needing a
> messaging protocol change or major sstable format (https://goo.gl/OvqNQp),
> and
> we currently have no branc
With 7 binding, 1 non-binding +1 votes and no -1's, the 2.2.8 release
vote passes. I will get the artifacts released. Thanks!
--
Michael
On 09/26/2016 08:12 AM, Gary Dusbabek wrote:
> +1
>
> On Fri, Sep 23, 2016 at 6:04 PM, Michael Shuler wrote:
>
>> I propose the
* NOTICE *
This is the first release signed with key 0xA278B781FE4B2BDA by Michael
Shuler. Debian users will need to add the key to `apt-key` and the
process has been updated on
https://wiki.apache.org/cassandra/DebianPackaging and patch created for
source docs.
Either method will work
there and 2) I really don't care
>>> about the branch name, 3.X just feels the more natural, but if something
>>> thing just calling it '3' or something else would be better, be my guest
>>> and rename it.
>>>
>>> On Tue, Sep 27, 2016 at 2
The votes were 8 +1 binding, 1 +1 non-binding, and no -1 votes. I will
get the release published.
--
Kind regards,
Michael
On 09/26/2016 09:52 AM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.8.
>
> sha1: ce609d19fd130e16184d9e6d37ffee4a1ebad607
>
The votes were 8 +1 binding, 1 +1 non-binding, and no -1 votes. I will
get the release published.
--
Kind regards,
Michael
On 09/26/2016 10:12 AM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.9.
>
> sha1: c1fa21458777b51a9b21795330ed6f298103b436
>
The votes were 8 +1 binding, 1 +1 non-binding, and no -1 votes. I will
get the release published.
--
Kind regards,
Michael
(with RESULT subject, this time)
On 09/26/2016 10:12 AM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.9.
>
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.8.
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
101 - 200 of 407 matches
Mail list logo
