So Rikard and I want to get the initial 2.0 work we've done out there before JavaOne. What's still holding us up is two things…
It's going to be in a new repo (svn), so just the logistics of preparing that and whatnot. I've personally never used svn either. (Not sure about Rikard) So maybe some questions there.
There's one place in the jme core that has a bit of bone related code that I'm not sure yet if we have permission to add.
I'll try to get some clarification on that second point, or refactor the code out of core asap. Could one of the other devs take charge of preparing and instructing us all on the new svn repo? I know we had some movement there, but not sure how we left it.
One other thing I'd like to clarify if it's not already clear… this code is not "2.0" release, it's more like a "2.0 pre alpha" release. There are a lot of structural changes (such as all the new enums), and many areas of new features and better opengl support. It also appears to run certain things a lot faster. But there's also a lot of things we wanted to do (new shader system, threaded rendering) before releasing even this much to the public that we just did not have the free time to do. We've been promising it for a long time though, and I know you all are anxious to get your hands on it as well. :) Sorry it's taken this long; with some of your help though it could be released this week.
If you're used to working with CVS in Eclipse, just install Subclipse. On the surface it will not feel very different at first… (of course SVN will enable you to do a lot things CVS can't and it will be faster to do large checkins and such). I also prefer Subclipse over the other Eclipse SVN plugin (forgot the exact name, EclipseSVN or something?).
As for a choice of repositories: do either java.net or google code (or some other host) offer SVN over HTTP access? (would be nice for people behing corporate firewalls)
I would agree that Google would be more reliable. Java.net has had a lot of problems over the years. In addition, we are likely to get a lot of extra hits given that we'll automatically be findable by search engines directly to our source code. They also have the ability to search the source code which might come in handy as well.