Engine Versions 3.3.x

Development
101

I agree with posting to 3.3.2, instead of trying to reallocate the 3.3.1 name. Here are a few reasons:

  1. Many users may have Gradle version ranges that could auto update to a newer point release.
  2. Even if we don’t see any complaints on the forum, it could still be impacting users. The jMonkey community is decently big - bigger that I though before I went looking, and much bigger than the volume of posts on the forum might indicate.

If we look at the bintray statistics (just jme-core, for example) we can see over 8000 downloads the last 30 days. Of course this could be many downloads by the same people, but dependencies are cached by Gradle so excessive downloading is minimized. That page also has some cool statistics, like 3.2.2 is still very popular! I wonder what’s preventing these users from using 3.2.4? Also, you can see we have a large international community :smiley:

Lets look at the SDK download stats - github has an api for this, though for some reason it isn’t used on the web view.

curl -s https://api.github.com/repos/jmonkeyengine/sdk/releases | egrep '"name"|"download_count"'

Looking at the recent 3.3.0 Beta 1 from Feb 6, we can see this:

"name": "jmonkeyplatform-linux-x64.sh",
        "download_count": 200,
        "name": "jmonkeyplatform-macosx.tgz",
        "download_count": 94,
        "name": "jmonkeyplatform-windows-x64.exe",
        "download_count": 881,
        "name": "jmonkeyplatform-windows-x86.exe",
        "download_count": 137,
        "name": "jmonkeyplatform.zip",
        "download_count": 150,

Not as much, but it is a prerelease - so that’s expected, right? If we go back to the 3.2.4 stable SDK release:

"name": "jmonkeyplatform-linux-x64.sh",
        "download_count": 1597,
        "name": "jmonkeyplatform-macosx.tgz",
        "download_count": 740,
        "name": "jmonkeyplatform-windows-x64.exe",
        "download_count": 9025,
        "name": "jmonkeyplatform-windows-x86.exe",
        "download_count": 1569,
        "name": "jmonkeyplatform.zip",
        "download_count": 1290,

Wow!

3 Likes
102

Agreed. Lets not spend an eternity discussing the minor details and provide endless obstacles on actually getting the job done.

1 Like
103

Simple, I expect the first dot release after 3.3.0 to be 3.3.1 :slightly_smiling_face:

Edit: Again this is just my opinion, please feel free to skip if you think it is a bad idea.

Having helped build the expectation of a 3.3.1-stable release, I’d love to satisfy it. Unfortunately, it’s no longer a good idea. I’ll explain why.

I’m ok with skipping it since it was visible for a couple hours… I’m also ok with reusing it because it is extremely unlikely anyone actually downloaded it during that time.

I downloaded it; that’s how I discovered it was defective. An automated e-mail announcing 3.3.1-stable was sent out to everyone watching the BinTray/JCenter page, including me. The possibility that someone downloaded should not be ignored. But maybe you’re right (as usual) and it never happened.

Unfortunately, even if nobody (other than me) downloaded it from JCenter, a release with that name is still available from JitPack. I won’t post the URL, but it’s easily found if you search. And I don’t see any way to remove it. It could be there for years.

Once a defective release is out in the world, creating competing releases with the same name will exacerbate the problem. Then, if someone reports an issue, it’ll be difficult to determine which release they’re actually using.

After sleeping on it, I’m convinced that we need to supersede 3.3.1-stable with a better release and call it 3.3.2-stable, even though it will disappoint a few people and leave a gap in the numbering.

Lets not spend an eternity discussing the minor details and provide endless obstacles on actually getting the job done.

Sorry for the delay. I’ll get to work on it now.

3 Likes
104

I clicked on the “Publish” button at GitHub. I’m waiting now for the build to complete and all 168 files to show up at BinTray.

2 Likes
105

Using my GitHub credentials, I logged into JitPack and deleted the 3.3.1-stable release. It was easier than I expected. So that risk is mitigated. There may be others.

3 Likes
106

The build completed and 174 files appeared at BinTray. I’m not sure yet where the 6 extra files came from. They weren’t there when I started.

107

I meant that in more of a “lets not have a 3 day discussion on 3.3.1 or 3.3.2 and let you do your thing” - and not a nudge to move faster. There’s no pressure on my end hurrying you up :slight_smile:

1 Like
108

I began looking through the packages at BinTray with unpublished files/items. jme3-examples had 6 (no Javadoc jar), which might explain the discrepancy. I’m still investigating.

Edit: There are 8 unpublished for jme3-testdata, which prior to 3.3.0-beta1 was unreleased. That brings the discrepancy down to 2. Still investigating.

Edit2: I searched BinTray as far back as the 3.2.3 release. It appears no Javadoc JAR has been published for jme3-examples in any recent releases. No one has complained, so I guess we can live with that oddity.

@pspeed, would you care to do the honors (of publishing the 174 items for the new release)?

109

I can… but I thought you had the permissions, too.

I will do it in 10-20 minutes if you haven’t done it yet.

1 Like
110

I have permissions. I suggested it as a gesture of trust and teamwork. Please, go ahead.

2 Likes
111

Done.

1 Like
112

Thanks.

113

JMonkeyEngine 3.3.2-stable is done, published, approved, anointed, etcetera:
Release jMonkeyEngine 3.3.2-stable · jMonkeyEngine/jmonkeyengine · GitHub

I couldn’t have done this alone. My heartfelt thanks to all who helped make it happen.

Now take it, go forth, and make cool things!

14 Likes
114

Grats @sgold :clap:! Time to edit my build files again to use new release :grinning:

1 Like
115

@jayfella, I submitted a PR to add a new blog post announcing the new release to the site.
Maybe you could have a look at it and comment on it.
https://github.com/jMonkeyEngine/website/pull/4
https://github.com/ItsMike54/website/blob/master/content/blog/jme3.3.2
Edit: And I made some changes, but the forums don’t seem to want to display them.

1 Like
116

It’s been 3 months since v3.3.2, and I haven’t heard any requests for a 3.3.3-stable release. I’m willing to create one if there’s a need.

Is anyone suffering from issues with the v3.3 branch—either working around them or being forced to run on JME’s master branch?

Not all issues can be addressed in v3.3, of course, but it seems worth asking…

4 Likes
117

I’m currently using master for PR Add ability to remove morph targets from mesh by tlf30 · Pull Request #1378 · jMonkeyEngine/jmonkeyengine · GitHub.

I think there was another fix but I cannot remember at the moment.

Thanks,
Trevor

1 Like
118

Thanks for that feedback.

In my opinion, PR 1378 can’t go into the v3.3 branch because it introduces new features. If people are using master for its features, then we should be discussing a v3.4 release.

119

RE a v3.4 release, v3.3.2-stable does not contain Expose ViewPorts by danielperano · Pull Request #1306 · jMonkeyEngine/jmonkeyengine · GitHub either. I’ve not hit any jME issues on v3.3.2-stable, and I’m definitely missing a few features on master. I’d be interested in discussing a v3.4 release sooner rather than later.

2 Likes