There has been awesome progress in jME lately. Especially my (the SDKs) interests are on the model import improvements and fixes. Also there are some really big changes in the horizon (jME 3.7 worthy?). So in my mind it starts to be a great slot to bake a jME 3.6.2. There are still some PRs left open and maybe they should too be included. I’m not proposing that by midnight today we have a new release out… no, rather to start discussion about the feasibility of this
I don’t even remember the process, was it to cherry pick stuff to 3.6 branch (or merge master to 3.6 branch?) or just tag one from master. This I guess would have a say on the outcome, that what jME 3.6.2 is supposed to look like.
i belive there already is milestone on github, and i guess once all milestone PRs are done then its merged into master and Tagged. While some of them(smaller fixes) were already merged before.
Im not sure if there were branches made first in the process.
The first step, I think, would be to identify low-risk bug fixes suitable for a 3.6.2 release.
I don’t even remember the process, was it to cherry pick stuff to 3.6 branch (or merge master to 3.6 branch?) or just tag one from master.
If we follow past procedures, the changes would be cherry-picked from the “master” branch into the “v3.6” branch, and the tag would be created in “v3.6”.
i thought “future release” is one for next release.
Do not mind me, process is not for me to determine. Its core devs to decide about process.
Just from user side it would be nice to see 3.6.2 milestone for example to know what will go in for next release. But i think there will be topic anyway where everyone could share opinion what could go into release.
There was only “future release” and few others. Should a milestone for 3.6.2 be done for selecting these low-risk bug fixes?
At this time, “future release” could refer to 3.7 or 4.0 . Creating a separate 3.6.2 milestone makes sense only if/when it’s decided there will be such a release. Otherwise, it’ll just create confusion.
