cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nate McCall <zznat...@gmail.com>
Subject Re: Rough roadmap for 4.0
Date Fri, 04 Nov 2016 21:40:27 GMT
Hi Stefan,
Thank you very much for bringing this up. I moved this to a new thread
because, though closely related, I think it is a very important
discussion to have on it's own as it does have a big impact.

Thanks,
-Nate

On Sat, Nov 5, 2016 at 9:15 AM, Stefan Podkowinski <spodxx@gmail.com> wrote:
> There has been a lot of discussions about diversity and getting new
> contributors and I think this aspect should be kept in mind as well when
> talking about a roadmap, additionally to the listed tickets that are
> already in the pipeline. What can inspiring developers contribute to 4.0
> that would move the project forward to it’s goals and would be very likely
> included in the final release? What should people work on that would not be
> left ignored, because there’s no need for it or no time to really take care
> of it?
>
> Same applies for reviewing tickets and I’m afraid the situations could get
> even worse with the recent organisational changes. If there are no goals on
> what should be included in 4.0, reviewers will probably just pick what they
> personally find relevant or related to what they already worked on. Other
> work will just be left ignored and I think that’s the worst thing to do
> while trying to build up a bigger developer community. Each contribution
> deserves some kind of response and even if it’s just a “not relevant for
> next release, will look into it another time” type of reply. Having clear
> goals or a certain theme for the release should make it easier to decide
> what to review and where to decline. Does that make sense?
>
> On Fri, Nov 4, 2016 at 3:47 AM, Nate McCall <zznate.m@gmail.com> wrote:
>
>> It was brought up recently at the PMC level that our goals as a
>> project are not terribly clear.
>>
>> This is a pretty good point as outside of Jira 'Fix Version' labelling
>> (which we actually suck less at compared to a lot of other ASF
>> projects) this really isnt tracked anywhere outside of general tribal
>> knowledge about who is working on what.
>>
>> I would like to see us change this for two reasons:
>> - it's important we are clear with our community about where we are going
>> - we need to start working more closely together
>>
>> To that end, i've put together a list (in no particular order) of the
>> *major* features in which I know folks are interested, have patches
>> coming, are awaiting design review, etc.:
>>
>> - CASSANDRA-9425 Immutable node-local schema
>> - CASSANDRA-10699 Strongly consistent schema alterations
>> - CASSANDRA-12229 NIO streaming
>> - CASSANDRA-8457 NIO messaging
>> - CASSANDRA-12345 Gossip 2.0
>> - CASSANDRA-9754 Birch trees
>>
>> What did I miss? What else would folks like to see? Specifically, this
>> should be "new stuff that could/will break things" given we are upping
>> the major version.
>>
>> To be clear, it's not my intention to set this in stone and then beat
>> people about the head with it. More to have it there to point it at a
>> high level and foster better communication with our users from the
>> perspective of an open source project.
>>
>> Please keep in mind that given everything else going on, I think it's
>> a fantastic idea to keep this list small and spend some time focusing
>> on stability particularly as we transition to a new release process.
>>
>> -Nate
>>

Mime
View raw message