I haven’t reviewed all the commits, but I believe @Darkchaos is correct that no major features have been added since the v3.3 branch.
I also agree with @pspeed that version numbers are free and major features aren’t a requirement for dot releases.
However, the various v3.3 releases ate up a ton of my time, not just to create/test/publish the builds themselves but also to maintain 2 versions of Minie and my other public libraries during the 9-month transition. Perhaps that won’t be necessary with v3.4; I don’t know. Releases also create work for those who maintain the SDK, the documentation, and so on.
So unless there’s enthusiasm for v3.4, I suggest waiting … until there is.
I’ve created milestones at GitHub for “v3.4.0” and “JCenter going down” so we can begin sorting and prioritizing Engine issues and PRs for the next release.
While the v3.4.0 milestone currently has no target date, this action will doubtless create some expectation of an actual release with that designation. Now is the time for those who care about the project to step up and volunteer:
I can help with publicizing, alpha testing (I can at least test existing footprint, and maybe some new features if I don’t have to expand our jME footprint too much to make use of new features), & PR reviews.
I am not so sure if I can really do something here , but let me try , I think jme3-jbullet the last time was not working , I will try reproducing the problem to find a fix , but unfortunately currently I am constrained to my exams , so 2-3 other weeks & I will be free.
You guys are really great, I really want to participate in it and carry out long-term maintenance, but I am really busy at the moment. I really want to modify the graphics rendering architecture of jme to support multiple rendering paths, and can specify the rendering path to be used from the material definition, such as using Forward or DeferredPath.
I’d love to see support for multiple rendering paths in JME. Unless we have something to test soon (next 3 weeks) I think that feature should appear in version 3.5, not 3.4.
Still looking for someone to update the documentation. I don’t want to issue another release with out-of-date documentation. It’s unkind to our users, and it places unnecessary load on the troubleshooters here at the Forum.
The milestone at GitHub is still a work in progress.
I’ll take care of issue 1388. (It’s fairly simple.) I’ll also create a change log for the release and post that to GitHub.
But documentation also includes the website and wiki, and those will surely need updating. For instance, I still can’t find any mention of light probes in the wIki. And the wiki’s instructions for importing models from MakeHuman are years out of date. I’d also like to see issue 96 closed. Furthermore, jme3-blender and jme-jogl will be gone from the Engine as of v3.4; the website and wiki should reflect that.
And that’s just what I know about. A careful review of the website and wiki might uncover more issues.
If we remove jme3-bullet and/or jme3-jbullet from the Engine, the website and wiki should reflect that.
And finally, if there’s no SDK v3.4, then the website and wiki should reflect that as well. (I certainly hope there will be an SDK v3.4, but nobody has volunteered yet.)
What about Nifty GuI , won’t we change that(we arenot going to remove it , but we must mention others) , you have now Lemur & javaFX on PCs & Lemur works on android too , but also you have Android views on android & it works fine without performance drop & I have proved that ,
notice that : anyone new to the engine have asked that question → How to create a game menu , pause menu
Besides , Some topics like how to make vegetations need to be provided with links to git repos , as well.