Yes new features are a big part of it and sometimes bug
fixes/improvements. Bug fixes are mostly due to being on trunk, but
some aren't necessarily introduced on trunk.  For e.g., we would like
to do a broader roll-out of the new producer, but KAFKA-2121 (adding a
request timeout to NetworkClient) actually blocks that effort. (The
reason for that being we have occasional broker hardware failures
given the size of our deployment which can actually cause producers
under certain circumstances to become wedged).

Joel

On Tue, Jun 23, 2015 at 09:54:30AM -0700, Gwen Shapira wrote:
> Out of curiosity, why do you want to run trunk?
> General fondness for cutting edge stuff? Or are there specific
> features in trunk that you need?
> 
> Gwen
> 
> On Tue, Jun 23, 2015 at 2:59 AM, Achanta Vamsi Subhash
> <achanta.va...@flipkart.com> wrote:
> > I am planning to use for the producer part. How stable is trunk generally?
> >
> > --
> > Regards
> > Vamsi Subhash
> >
> > --
> >
> >
> > ------------------------------------------------------------------------------------------------------------------------------------------
> >
> > This email and any files transmitted with it are confidential and intended
> > solely for the use of the individual or entity to whom they are addressed.
> > If you have received this email in error please notify the system manager.
> > This message contains confidential information and is intended only for the
> > individual named. If you are not the named addressee you should not
> > disseminate, distribute or copy this e-mail. Please notify the sender
> > immediately by e-mail if you have received this e-mail by mistake and
> > delete this e-mail from your system. If you are not the intended recipient
> > you are notified that disclosing, copying, distributing or taking any
> > action in reliance on the contents of this information is strictly
> > prohibited. Although Flipkart has taken reasonable precautions to ensure no
> > viruses are present in this email, the company cannot accept responsibility
> > for any loss or damage arising from the use of this email or attachments

Reply via email to