lidd: there was a critical problem which held up 3.1 -- it was not an easy problem to diagnose, and in fact it was an existing problem in 3.0.5, but having the fix was deemed important enough to hold up the release.
In the meantime, we also were able to integrate some new functionality (thereby avoid an interim micro release) for VAAI, and disk management support (giving better visual management capabilities for JBODs.)
So while the delay was very unfortunate, ultimately, we did what we felt was right for our customers.
July 27, 2011 at 1:11 PM
NexentaStor 3.0.5 is now available. Apart from fixing some key bugs, the main thing that this release includes is a significant update to the CIFS stack, which addresses both performance concerns, and AD failover concerns. Note that NS 3.1 is due out *any day now*, and will include all these changes, plus a boat load of others. I'll have a lot more to say about the 3.1 release soon.
posted by Garrett D'Amore at 2:42 PM on May 2, 2011
"NexentaStor 3.0.5 available now"
5 Comments -
here are the release notes:
http://www.nexenta.com/corp/images/stories/pdfs/release_notes_3.0.5.pdf
May 2, 2011 at 2:48 PM
Thanks although we didn't ran into the bugs mentioned, they're appreciated :-)
This update came almost in perfect time for a reboot. (Also that 3.0.5 core sources have been published in nexenta-gate)
May 6, 2011 at 1:18 AM
I'm waiting eagerly for NexentaStor 3.1 - is there any news on its progress?
June 13, 2011 at 3:04 AM
3.1 "Any day now"? 5 days ago the bits were being published? This is not especially confidence inspiring.
July 27, 2011 at 10:54 AM
lidd: there was a critical problem which held up 3.1 -- it was not an easy problem to diagnose, and in fact it was an existing problem in 3.0.5, but having the fix was deemed important enough to hold up the release.
In the meantime, we also were able to integrate some new functionality (thereby avoid an interim micro release) for VAAI, and disk management support (giving better visual management capabilities for JBODs.)
So while the delay was very unfortunate, ultimately, we did what we felt was right for our customers.
July 27, 2011 at 1:11 PM