With the Hudson builder set up and working, we feel it is time to finally release a stable package for JME 2.0. This release should bring several benefits, such as:
Announcing the newest 2.0 release is great publicity.
Newcomers who prefer to download the package instead of pulling the dev-release from the SVN will now get a much more up-to-date release.
Anyone who wants to update our documentation can finally refer to the stable package release in their doc revisions.
Feature-developers will now have a dedicated development branch (probably 2.1), for which there will be nightly builds.
Before making the final build and release, we are giving the everyone a weeks notice to:
finalize code, if anyone happened to have left any WIPs in the trunk
address issue tickets you consider a priority for a valid stable
make last-minute tickets to point out urgent major issues - this should be done within a day or two, so there's time to address it.
generally just speak your mind if you think we're stepping on toes or ignoring something here.
Lastly, for any contributor who committed a multitude of changes or some of great significance, we would greatly appreciate it if you could look as far back as possible and make a personal changelog of your commits. You could then pass this changelog on to me (either just post it here or mail it to me) and we would compile everything together into one unified changelog with appropriate credits. This type of changelog is probably just a one-time thing, considering we had such a great gap between the last stable release and the upcoming one.
how about a wiki page for the change log , that way everyone could easily add missing items.
I'm well aware of it, but it seems like people haven't really 'chipped in' for it, hence the call for more direct contributions. It would all end up in that page in the end though.
I see no section on the wiki page for this. There is just a “1.0 to 2.0” section and a 2.1 section, and it looks like this new stable release will not be labelled 2.1.
For example, this probably isn't pertinent to a release:
4516 7/17/09 9:24 PM 13 blaine.dev Added basic Matrix function missing from Python API. Some fixes to properly support multiple skins. Fixed writing of SkinNode component spatials to precisely match jME native.
while this I think would be appropriate:
4556 7/27/09 6:05 PM 1 blaine.dev Fixed bug accidentally introduced to do with export of armatures
I see no section on the wiki page for this. There is just a "1.0 to 2.0" section and a 2.1 section, and it looks like this new stable release will not be labelled 2.1.
Nope, that was not the plan anyways. If you think it justifies the "2.1" label already we could discuss that.
I see no section on the wiki page for this. There is just a "1.0 to 2.0" section and a 2.1 section, and it looks like this new stable release will not be labelled 2.1.
Nope, that was not the plan anyways. If you think it justifies the "2.1" label already we could discuss that...
No. As the goal is to get the change log bullets onto that Wiki page, and as I am competent at both change log bullets and our wiki, I was going to cut out the middle man, as suggested by Core-Dump and and which you had no objection to. If I am to edit the wiki, I want to do it where and how you want me to.
Would it be acceptable if I make a new section, and you can change the section titile, formatting, or content as you see fit?
Would it be acceptable if I make a new section, and you can change the section titile, formatting, or content as you see fit?
That sounds just fine. Thanks for your cooperation!
I've added my items. Pretty numerous for one contributor, but not unexpected considering the duration represented.
I probably have numerous typos, etc., in there. It took a lot of work to go through all of those logs. I'll proof read and fix when I can stomach it again. UPDATE: Proofed. If anybody fixed my entries in between, thanks!
Please don't release JME 2.0 now. I would prefer to fix some important things in the JOGL renderer before.
If you can provide us with a fairly accurate ETA on your fixes then we could consider it, if else you can just submit it to 2.1, which isn't such a big deal seeing as most 'developers' as opposed to first timers will usually be using the development branch anyways.
blaine said: I've added my items. Pretty numerous for one contributor, but not unexpected considering the duration represented.
I probably have numerous typos, etc., in there. It took a lot of work to go through all of those logs. I'll proof read and fix when I can stomach it again. UPDATE: Proofed. If anybody fixed my entries in between, thanks!
I think there was a single typo or misplaced space or something when I threw my meager contributions in there. btw, very impressive list! thanks for all your hard work :)
Please give me 24 hours notice before rolling the stable. I just found FloatBuffer problems in SkinNode which may account for some problems which have been stressing me out for 6 months.
Please give me 24 hours notice before rolling the stable. I just found FloatBuffer problems in SkinNode which may account for some problems which have been stressing me out for 6 months.
Erlend will send out an email or pm a day or two before of course.. Which, by the way, begs the question.. Who else besides blaine and Core-Dump should be personally notified right before the release?
If the new download is indeed "2.0.1", it should be distinguished as such somewhere on the download page. It looks like somebody's preference is to just show the Subversion revision. That is pretty uninformative for most users and will be downright confusing once we have multiple stable choices available at the same time, like 2.0.2, 2.1.2, 3.0.1, 2.2.1,... Maybe the idea is to only offer one stable for each "series". In that case the "2.0" series file name still needs to be differentiated from 2.1, etc.
UPDATE: Applications intended to be platform-independent shouldn't use shell metacharacters like () in file names.
Thanks for the work putting this together, erlend.
FYI I am also going to be requesting a couple changes for our entry at Devmaster.net. With the changelog and forum I should have a pretty good idea of what needs to be updated, but if you know of something that I might miss or something that you can’t have me miss, just make a note of it here.
