Why wouldn't you keep a bug free version of something in production? If I found a version of *anything* that was bug free I don't think I'd ever upgrade again.
On Fri, Jan 8, 2016 at 9:18 AM Anuj Wadehra <anujw_2...@yahoo.co.in> wrote: > Thanks Robert !!! > > *"I don't run X.Y.Z versions where Z is under 6, so in general this does > not result in me not-running-a-version-I-otherwise-would-have for longer > than a few months each year."* > Agree !! But, if you upgrade to a version greater than X.Y.6, and then it > goes EOL within months, you won't like to keep that version in Production > even if it's bug free. > > Thus, like some of the other Apache Open Source products, I think > following points are worth considering: > > 1. EOL should be based on "most stable"/"production ready" version date > rather than "GA" date of subsequent major releases. > 2. I think we should have "Formal EOL Announcement" on Apache Cassandra > website. > 3. "Formal EOL Announcement" should come at least 6 months before the EOL, > so that users get reasonable time to upgrade. > 4. EOL Policy (even if flexible) should be stated on Apache Cassandra > website > > Please share your feedback. > > Thanks > Anuj > > > On Friday, 8 January 2016 12:07 AM, Robert Coli <rc...@eventbrite.com> > wrote: > > > On Wed, Jan 6, 2016 at 5:26 PM, Anuj Wadehra <anujw_2...@yahoo.co.in> > wrote: > > I would like to understand how various users are dealing with the > situation. Are you upgrading Cassandra every 3-6 mths? How do you cut short > your planning,test and release cycles for Cassandra upgrades in your > application/products? > > > I upgrade Cassandra an average of once a year. > > I don't run X.Y.Z versions where Z is under 6, so in general this does not > result in me not-running-a-version-I-otherwise-would-have for longer than a > few months each year. > > There is really not that much penalty to being behind the curve, in fact > there is often a significant penalty to being on the cutting edge. > > =Rob > > > >
