+1, please try out our latest release line whenever thinking about moving up. This is currently 1.1.x. Over time we will be end-of-lifing old release lines as we introduce newer minor and major releases, and will most likely be doing so from oldest first.
On Tue, Aug 25, 2015 at 9:54 AM, Nick Dimiduk <[email protected]> wrote: > Unless you've observed some serious issue preventing you from doing so, I > would suggest adopting the newest release available. If you're a > particularly conservative lot, perhaps choose one previous. The 0.98 and > branch-1 releases are all rolling-upgradable between them, so upgrading > production should be relatively painless. For my part at 1.1 RM, I plan to > continue with regular patch releases as long as bug fixes are back-ported, > or until 1.2 is released and matured. That said, we're pushing out nice new > features with each minor release and the only way to get them is to > upgrade. > > On Mon, Aug 24, 2015 at 2:41 AM, Yu Li <[email protected]> wrote: > > > Hi All, > > > > As titled, now we're using 0.98.12 in our product env but would like to > do > > some planing for upgrading to branch-1. I could see 1.1.2 is coming soon > > but 1.2 is also in progress w/ some important improvements, so my > question > > basically includes two parts: a) If for planning (not action), which one > is > > better for investigation? 1.1.2 or 1.2? and b) Is there a due date for > 1.2? > > > > Also, I've heard that some famous company is planning to upgrade their > > product cluster to 1.2, and it would be great if anyone could confirm > this > > or share more information. :-P > > > > Any suggestions/information would be highly appreciated, and thanks in > > advance! > > > > > > Best Regards, > > Yu > > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
