Re: Testing and jira tickets

2017-04-11 Thread mck 

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 example, should contributors/committers run dtests and unit tests on
> *some* machine (publicly available or otherwise), and then post those
> results to the ticket?


Yes please.
 I'm a supporter that nothing should get committed without it passing
 both unit and dtests.
 That any SHA in trunk or any release branch that fails unit or dtests
 is automatically uncommitted (reverted).

I was under the impression that the point of tick-tock was to move the
code towards a stable master approach. And that the lesson learn that
restricting any release to only have one patch version is: regardless of
how good the developers and CI system is; a pretty poor way of trying to
build a stable product. 

So from tick-tock to 4.0, I was really hoping it meant keeping all the
stable master and CI improvements obtained throughout the tick-tock
cycle while re-adding the discipline of ongoing patch versions to
supported releases. (While being realistic to resources available.)


Unfortunately without access to DS' cassci the best that i could do is
this:
  
https://issues.apache.org/jira/browse/CASSANDRA-13307?focusedCommentId=15962001=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#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

Re: [VOTE] Release Apache Cassandra 3.0.13

2017-04-11 Thread Jeff Jirsa 
+1

-- 
Jeff Jirsa


> On Apr 11, 2017, at 11:59 AM, Michael Shuler  wrote:
> 
> 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/apache/cassandra/apache-cassandra/3.0.13/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1142/
> 
> The Debian and RPM packages are available here:
> http://people.apache.org/~mshuler/
> 
> The vote will be open for 72 hours (longer if needed).
> 
> [1]: (CHANGES.txt) https://goo.gl/xBbbHa
> [2]: (NEWS.txt) https://goo.gl/PlsFmm

Re: [VOTE] Release Apache Cassandra 3.0.13

2017-04-11 Thread Nate McCall 
On Wed, Apr 12, 2017 at 6:59 AM, Michael Shuler  wrote:
> I propose the following artifacts for release as 3.0.13.
>
> sha1: 91661ec296c6d089e3238e1a72f3861c449326aa

+1

[VOTE] Release Apache Cassandra 3.0.13

2017-04-11 Thread Michael Shuler 
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/apache/cassandra/apache-cassandra/3.0.13/
Staging repository:
https://repository.apache.org/content/repositories/orgapachecassandra-1142/

The Debian and RPM packages are available here:
http://people.apache.org/~mshuler/

The vote will be open for 72 hours (longer if needed).

[1]: (CHANGES.txt) https://goo.gl/xBbbHa
[2]: (NEWS.txt) https://goo.gl/PlsFmm