Fwiw, Duke just gets easily excited about these things 
Anyway, I'm anticipating the next stable release. Like I said, I'm writing a document that needs an up to date version of Dolphin, but the GIT releases are moving targets essentially, so I'm frequently updating various sections all over again. 3.0 is too old to use for my purposes since the next official release would require a massive rewrite when it comes out.
Name it 3.5 if you guys feel the next stable release will be out in a year or so, 3.9 if 4.0 is just around the corner. I don't think versioning is arbitrary; it should reflect the developers' estimate of progress but it should also give users hints about how relatively far along the project is until the next release if it's not a X.0 build. 3.9 seems like there's just a little left to do in order to reach 4.0, that's the message it sends to me. A lot of (clueless) people might start to get impatient for 4.0; that already happens, but having a stable release at 3.9 might just make it worse :p
Anyway, I'm anticipating the next stable release. Like I said, I'm writing a document that needs an up to date version of Dolphin, but the GIT releases are moving targets essentially, so I'm frequently updating various sections all over again. 3.0 is too old to use for my purposes since the next official release would require a massive rewrite when it comes out.
Name it 3.5 if you guys feel the next stable release will be out in a year or so, 3.9 if 4.0 is just around the corner. I don't think versioning is arbitrary; it should reflect the developers' estimate of progress but it should also give users hints about how relatively far along the project is until the next release if it's not a X.0 build. 3.9 seems like there's just a little left to do in order to reach 4.0, that's the message it sends to me. A lot of (clueless) people might start to get impatient for 4.0; that already happens, but having a stable release at 3.9 might just make it worse :p