I believe 3.2.4 is built and deployed, but I’m not sure, since the OS X build hit Travis’s 10-minute timeout near the end: Travis CI - Test and Deploy Your Code with Confidence
@pspeed42, if you see the usual 166 new files, please click on the button to make them publicly available. Otherwise, let me know and I’ll retry the build.
166 items have been published.
I had the same issue with my sdk build.
Would you mind restarting the tag build?
I cannot access travis because it wont log me in due to an “expired token”
You want me to restart the SDK build?
Thank you, @pspeed! I’ll write up some release notes.
Here you go…
Release jMonkeyEngine 3.2.4-stable · jMonkeyEngine/jmonkeyengine · GitHub
Yes please, because it also got killed due to the “10 minutes no output”, which I guess happened because of a travis issue (slow server or something).
I’ll try to get my travis account back in the meantime
Hooray!
The build was successfully restarted.
If there’s ever a JME v3.2.5, it ought to include PR 1146, the fix for issue 1167.
The v3.2.4 jme3-bullet-native-android library contains out-of-date native libraries (last built in November), so there’s another reason we should release a v3.2.5 of the Engine.
I’ll review master commits since July to see if there’s anything else worth backporting to the v3.2 branch.
Update: I found one, a fairly minor bug. Issue 1188
BTW, since apparently I’m the de facto release manager for 3.3, I’m trying to work towards a branch + beta release “soon”.
I will ultimately need help with release notes, etc… but I can walk things through the beta process. I’d like to spend minimal amount of time in beta if possible.
I will be taking a week off from “day job” at the end of November and would like to try to wrap things up that week if possible.
In case you like I would be happy to help you with anything going around the new animation system. I have some ideas going in my head around overhauling the new animation system to end up to be a 1:1 mapping of Lemur animation system.
Sounds good but I would have two questions:
If you think about it, once you have your ideas together (and it sounds like you do), you might see if you can evoke the spirit of nehon and run the ideas/assumptions/questions by him just in case he has anything inspirational to say.
No, it’s all about making the new animation system’s API a bit cleaner and make exclusive use of Lemur animation system rather than playing everything in AnimComposer.
Simply put, like we have SpatialTweens, CameraTweens,… we are going to also have AnimTweens for creating animation specific tweens (ClipAction, BlendedAction).
Probably not that soon. I guess it will introduce breaking changes to classes in com.jme3.anim.tween.action package. (not the loaders)
I am going to first implement my idea locally and when satisfied and fully tested I will make a new post about it so we can discuss it in more detail.
If I’m able to wrangle the time away from “life”, I plan to create the 3.3 branch tomorrow and the beta1 tag. If I don’t get to it tomorrow then it will be next week end.
This is all trying to work towards wrapping up a 3.3 release near the end of November.
I don’t see a v3.3 branch, nor a v3.3.0-beta1 tag. @pspeed what’s your current thinking regarding the 3.3 release?
I had other things get in the way on the days that I planned to do it and also the build seemed to be in flux so I wasn’t 100% sure things would work for me.
I’m off for a week starting Friday night and plan to kick the 3.3 release into gear during that time if no one has made the branch + tag before then.
More details on this.
I only just got started on my “game dev” vacation and I’m taking another one at the end of December.
As I get back into my projects, I’m finding last minute things I want to tweak/add to JME, etc. but will probably try to do a dry run for beta1 soon. Plan is to get beta1 out this week for a real release when I’m off again at the end of December… depending on how things go.
Edit: for example, after 7+ years of using the engine, I finally hit a case where some constant gets modified and starts corrupting things and it’s not obvious where… so I made this:
I made the 3.3 branch and created the 3.3.0-beta1 tag but I guess the automated builds don’t build releases anymore. That’s a “bridge too far” for me so further action will have to wait until that is fixed or someone else takes up the reigns.
the build had to be triggered with the release feature in github. it should build now.
Thanks, I’ll keep an eye out on bintray for the uploads.