2.1.3 has a few memory leaks/issues, resource management race conditions. That is horribly vague, however looking at some of the fixes in 2.1.4 I’d be tempted to wait on that.
2.1.3 is fine for testing though. > On Mar 9, 2015, at 6:42 PM, Jacob Rhoden <jacob.rho...@me.com> wrote: > > I notice some of the discussion about rolling back and avoiding upgrading. I > wonder if people can elaborate on their pain points? > > We are in a situation where there are some use cases we wish to implement > that appear to be much simpler to implement using indexed sets. So it has me > wondering about what the cons would be of jumping into 2.1.3, instead of > having to code around the limits of 2.0.x, and then re-write the features > once we can use 2.1.3. (Ideally we want to get these use cases into prod > within the next 4 weeks) > > Thanks, > Jacob
smime.p7s
Description: S/MIME cryptographic signature
