Yeah I'd be in favor of a quicker, smaller release but I think as long as we have these big things in flight we should probably keep the release criteria feature-based rather than time-based, though (e.g. "when X works" not "every other month).
Ideally the next release would have at least a "beta" version of the new consumer. I think having a new hunk of code like that available but marked as "beta" is maybe a good way to go, as it gets it into peoples hands for testing. This way we can declare the API not fully locked down until the final release too, since mostly users only look at stuff after we release it. Maybe we can try to construct a schedule around this? -Jay On Wed, Mar 11, 2015 at 7:55 PM, Joe Stein <joe.st...@stealth.ly> wrote: > There hasn't been any public discussion about the 0.8.3 release plan. > > There seems to be a lot of work in flight, work with patches and review > that could/should get committed but now just pending KIPS, work without KIP > but that is in trunk already (e.g. the new Consumer) that would be the the > release but missing the KIP for the release... > > What does this mean for the 0.8.3 release? What are we trying to get out > and when? > > Also looking at > https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan > there > seems to be things we are getting earlier (which is great of course) so are > we going to try to up the version and go with 0.9.0? > > 0.8.2.0 ended up getting very bloated and that delayed it much longer than > we had originally communicated to the community and want to make sure we > take that feedback from the community and try to improve upon it. > > Thanks! > > ~ Joe Stein > - - - - - - - - - - - - - - - - - > > http://www.stealth.ly > - - - - - - - - - - - - - - - - - >
