> I am fine with Jenkins or CircleCI; though I feel CircleCI is more effort
> for each member.
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
> Moving to pure pipeline jobs with all build & test runs in one pipeline,
> with a final single JIRA comment post operation of all the results in
> one comment would be the only way I can think of to prevent the
> multi-post problem.
For the pipeline build, this is what I have so far puttin
> Just committing, watching for
> errors in the seed job and fixing them isn't very problematic. The
> existing jobs are not touched, if the DSL does not parse correctly, and
> the errors are usually pretty clear where the issue might be. Just do it
> in prod, once it looks about what we want
Jeff,
the use of the terms "business concerns" and "technical merit" may be an
unfortunate choice I made, they can be construed in a narrower way than I
intended and i apologise Jeff for that confusion. Our community and how we look
after it does matter.
The hope I raised was only that we dea
> Let met just say that as an observer to this conversation -- and someone
> who believes that compatibility, extensibility, and frankly competition
> bring out the best in products -- I'm fairly surprised and disappointed
> with the apparent hostility many community members have shown toward a
>
> I propose the following artifacts for release as 3.11.2.
Thanks Michael for the recut, very much appreciated.
+1
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cass
> I propose the following artifacts for release as 3.11.2.
> …
> The vote will be open for 72 hours (longer if needed).
I just pushed the back-port of CASSANDRA-13080 (under CASSANDRA-14212).
This is the improvement "Use new token allocation for non bootstrap case as
well".
We've seen that this
> There's also no way for us to label, assign or otherwise use PR related
> features, so I'm really wondering why it would make sense to more
> heavily using them.
Apache does now offer the GitBox service. This makes the github repository
writable. The asf and github repos are kept in sync, rat
> I can do this tomorrow if I hear no objections.
Done.
regards,
Mick
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
On Sat, 29 Apr 2017, at 01:14, Michael Shuler wrote:
> 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 s
Has anyone any objection to moving all open 3.11.x features and
improvements to 4.0?
To my understanding 3.11.0 was intended as the last tick-tock release
and also to form a LTS release by which patches could be applied, ie
3.11.1, 3.11.2, 3.11.3, etc.
As the last tick-tock release there's a
anel#comment-15962001
And running dtests on ASF's Jenkins was a 30hr turn around.
:panda_face:
Is there any hope here for us that don't have access to cassci?
~mck
http://cassandra.apache.org/doc/latest/development/index.html
This is fantastic. Thanks heaps and heaps for doing this.
Stefan i believe you get some of the credit for this!
The top level 'Community' link now seems a bit superfluous. I guess
there are plans for this?
There's also no docs on h
> Please vote
+1 (non-committer)
~mck
14 matches
Mail list logo
