Hi Jim, Thanks for your feedback. We value the community and we definitely want Kafka to remain a fun and friendly place to participate. Under this proposal, volunteers will still be able to do the work when they can. The benefit is that it is likely to reach users faster since the next release is never far away.
Ismael On Tue, Aug 16, 2016 at 2:42 PM, Jim Jagielski <j...@jagunet.com> wrote: > The idea of time-based releases make sense. The issue is > when they become the tail wagging the dog. > > Recall that all developers and contributors are assumed to > be doing this because they are personally invested in the > project. Their is also the assumption that, as such, they > are volunteers and do the work "when they can". And finally, > there is the fact that working on Apache projects should be > FUN. It should be someplace where you aren't beholden to, > or under, some artificial schedule. > > If time-based releases are put in place, and held to under > unforgiving standards, all the above are put at risk. And > when that happens it puts the project and the community at > risk as well. > > So having a set schedule is fine... it's how "we" do it that > is key. >