Guidelines for test coverage

2016-09-19 Thread sankalp kohli 
Hi,
I wanted to know if there are any guidelines for contributors to give
out unit and integration tests along with the patches. If not, we should
discuss and have them in place.

I know we are making good progress with test coverage but we should add
guidelines around adding unit and integration tests with every patch.
Thoughts on this?

Thanks,
Sankalp

Re: Proposal - 3.5.1

2016-09-19 Thread Eric Evans 
On Fri, Sep 16, 2016 at 5:05 AM, Sylvain Lebresne  wrote:
> In light of all this, my suggesting for a release cycle woud be:
> - To have 3 branches: 'features', 'testing' and 'stable', with an X month
>   rotation: 'features' becomes 'testing' after X months and then 'stable'
> after
>   X more, before getting EOL X months later.
> - The feature branch gets everything. The testing branch only gets bug
> fixes.
>   The stable branch only gets critical bug fixes. And imo, we should be very
>   strict on this (I acknowledge that there is sometimes a bit of
> subjectivity on
>   whether something is a bug or an improvement, and if it's critical or
> not, but
>   I think it's not that hard to get consensus if we're all reasonable
> (though it
>   might worth agreeing on some rough but written guideline upfront)).
> - We release on a short and fixed cadence of Y month(s) for both the
> feature and
>   testing branch. For the stable branch, given that it already had X months
> of
>   only bug fixes during the testing phase, one can hope critical fixes will
> be
>   fairly rare, less than 1 per Y period on average). Further, it's supposed
> to
>   be stable and fixes are supposed to be critical, so doing hot-fix releases
>   probably makes the most sense (though it probably only work if we're
> indeed
>   strict on what is considered critical).

This seems pretty close to what Mck suggested; I think this could work.


-- 
Eric Evans
john.eric.ev...@gmail.com

Re: Proposal - 3.5.1

2016-09-19 Thread Eric Evans 
On Thu, Sep 15, 2016 at 9:33 PM, Mick Semb Wever  wrote:
>  - keep bimonthly feature releases,
>  - revert from tick-tock to SemVer numbering scheme,
>  - during the release vote also vote on the quality label (feature branches
> start with a 'Alpha' and the first patch release as 'Beta'),
>  - accept that every feature release isn't by default initially supported,
> and its branch might never be,
>  - maintain 3 'GA' branches at any one time,
>  - accept that it's not going to be the oldest GA branches that necessarily
> reach EOL first.

I like it.

-- 
Eric Evans
john.eric.ev...@gmail.com

[VOTE RESULT] Release Apache Cassandra 3.0.9

2016-09-19 Thread Jake Luciani 
With 11 binding +1, 5 non-binding +1 and no -1 the vote passes. I will
publish.

On Mon, Sep 19, 2016 at 2:19 AM, Tommy Stendahl  wrote:

> +1 (non binding)
>
>
>
> On 2016-09-15 20:57, Jake Luciani wrote:
>
>> I propose the following artifacts for release as 3.0.9.
>>
>> sha1: d600f51ee1a3eb7b30ce3c409129567b70c22012
>> Git:
>> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=sho
>> rtlog;h=refs/tags/3.0.9-tentative
>> Artifacts:
>> https://repository.apache.org/content/repositories/orgapache
>> cassandra-1124/org/apache/cassandra/apache-cassandra/3.0.9/
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapache
>> cassandra-1124/
>>
>> The artifacts as well as the debian package are also available here:
>> http://people.apache.org/~jake
>>
>> The vote will be open for 72 hours (longer if needed).
>>
>> [1]: https://goo.gl/JKkE05 (CHANGES.txt)
>> [2]: https://goo.gl/Hi8X71 (NEWS.txt)
>>
>>
>


-- 
http://twitter.com/tjake

Re: [VOTE] Release Apache Cassandra 3.0.9

2016-09-19 Thread Tommy Stendahl 

+1 (non binding)


On 2016-09-15 20:57, Jake Luciani wrote:

I propose the following artifacts for release as 3.0.9.

sha1: d600f51ee1a3eb7b30ce3c409129567b70c22012
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.9-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1124/org/apache/cassandra/apache-cassandra/3.0.9/
Staging repository:
https://repository.apache.org/content/repositories/orgapachecassandra-1124/

The artifacts as well as the debian package are also available here:
http://people.apache.org/~jake

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

[1]: https://goo.gl/JKkE05 (CHANGES.txt)
[2]: https://goo.gl/Hi8X71 (NEWS.txt)