Hello everyone! First, I apologize for the aborted 2.12 release. We
got as far as rolling it but I decided to make a real push to try to
fix the occassional random seg-fault bug that we were still seeing
on 64-bit at the time.
The seg-fault issue has now been resolved, I post
Best of luck for the forthcoming release and merry xmas and happy new year!
Just waiting whether multimaster in HAMMER ;-)
zenny
On 12/26/11, Matthew Dillon wrote:
> Hello everyone! First, I apologize for the aborted 2.12 release. We
> got as far as rolling it but I decided to make a
Not that my voice has any weight, but I applaud and welcome a 3.0
release. :)
-Toby.
On Sun, Dec 25, 2011 at 4:01 PM, Matthew Dillon
wrote:
> Hello everyone! First, I apologize for the aborted 2.12 release. We
> got as far as rolling it but I decided to make a real push to try to
> f
On Sun, Dec 25, 2011 at 6:01 PM, Matthew Dillon
wrote:
> Hello everyone! First, I apologize for the aborted 2.12 release. We
> got as far as rolling it but I decided to make a real push to try to
> fix the occassional random seg-fault bug that we were still seeing
> on 64-bit at the
On Sun, Dec 25, 2011 at 6:01 PM, Matthew Dillon
wrote:
> (2) I would like to call the release 3.0. Why? Because while
> spending the last ~1-2 months tracking down the cpu bug a whole lot
> of other work has gone into the kernel including major network
> protocol stack wo
On Mon, 2 Jan 2012 00:37:58 -0500
Justin Sherrill wrote:
> On Sun, Dec 25, 2011 at 6:01 PM, Matthew Dillon
> wrote:
> > (2) I would like to call the release 3.0. Why? Because while
> > spending the last ~1-2 months tracking down the cpu bug a whole
> > lot of other work has gone into
On Mon, Jan 2, 2012 at 1:59 AM, Steve O'Hara-Smith wrote:
> Whatever happened to the old principle for three part numbers
>
> ..
>
> Bug fix releases bump the fix level, new features bump the feature
> level and zero the fix level, big changes that break backwards
> compatibility bum
