It's time to release 0.9.5

[Vadim]

Hi everybody,
I think we should freeze any development on 0.9.5. If we continue to modify branch's code, we never release new version. It is time to stop. If nobody knows some critical bugs in branch (such as application crashes, etc), we can build MMEX for all platforms and publish one. All detected bugs, new features and others things we will continue to do in main trunk of development. I everyday use MMEX from trunk (its version marked as 0.9.6) and do not have any bugs and problems. So, we could publish 0.9.6 very soon after 0.9.5, for example, Christmas Edition And this version will incorporate bugfixes for bugs found in 0.9.5.

[Nikolay]

+2

[Nikolay]

Is any step by step instractions for newbie ?

[Vadim]

I can build setup of mmex from branch for all Windows. Also I can build mmex on Fedora-11. But in latter case I'm not sure that my version will run on any others Unix-es. Also I cannot build mmex for Ubuntu and SUSE, so we need someone who build mmex on these platforms. And our mate elliswr can build 0.9.5 for Mac.

When we get all builds we can do final tests (for example, install mmex from scratch and test basic functionality).
Next step will be upload binaries on site and sourceforge and update content of site http://www.codelathe.com/mmex. But I don't know who can do this except Madhan.

[Vadim]

Also someone should update versions of mmex in resources and files, update readme and release notes. I think Nikolay can do it.

P.S. I have already done this.

[mrgingles]

Waiting for the official relase of MMEX 0.9.5, I agree with Vadim...

[omalleypat]

When we do release it, we should make a copy of the branch to the tags folder. It looks like this hasn't been done in a while for past releases.

[Vadim]

I know what to do, don't worry I planned to copy 0.9.5 to tags\release today, but I've found a critical BUG for one minute of using mmex (in debug build click on "Notes" column's header). This bug absent in trunk. I don't do any work in branch, so I thought 0.9.5 ready to release. But now I have to check main functionality personally. Use Debug builds in your work, mates! It's not a proposition, it's requirement.

[madhan]

Thats great.

I will also personally test the build.
Lets make sure we get enough mileage on it before it is released.

Some of the main requirements before a release is that
1) It should be backwards compatible with databases from older releases, load it properly
2) All major functionality should work as before, adding/removing/listing transactions, importing etc

Next step will be upload binaries on site and sourceforge and update content of site http://www.codelathe.com/mmex. But I don't know who can do this except Madhan.

Yes, that should be no problem. We can work on other options in the future if needed.
Please send me a PM if you need me to do any work and I am not on the forums. I check forums every few days.

I would like to keep the CodeLathe site as a hub for MMEX and not source forge for several reasons, chief among them being the shameless plug for traffic for my startup.

[madhan]

Also, can we all freeze SVN checkins into the branch unless absolutely required.

[Nikolay]

I've found a critical BUG for one minute of using mmex (in debug build click on "Notes" column's header).

I have fixed the problem in svn 699

Use Debug builds in your work, mates! It's not a proposition, it's requirement.

I love the project anymore

[Nikolay]

After start debuging all seems ok, but when I closed the app I have got the following message:

BTMMHOOK 30.10.2009 08:49:29 Thread<0FD8> Hook DLL loaded
"mmex.exe": Загружено "C:\Program Files\DigitalPersona\Bin\DpOSet.dll"
BTMMHOOK 30.10.2009 08:49:39 Thread<0FD8> Hook DLL unloaded
Detected memory leaks!
Dumping objects ->
{1742} normal block at 0x01402EF8, 48 bytes long.
Data: <( , > 28 00 00 00 00 00 00 00 18 2C 16 00 FF FF FF FF
Object dump complete.
Программа "[4024] mmex.exe: Машинный код" завершилась с кодом 0 (0x0).

[Vadim]

This leak is well-known for me I will find this leak in the future I think.

[Vadim]

So, what should we do now. We have this weekend to test 0.9.5. No more changes in branch except bugfixes if we find ones. If everything will be ok, the head revision of branch will be final release of 0.9.5 on next week.

[elliswr]

We need to change the "check for new version" link back to Codelathe's webpage. I would do it myself, but I just don't have the time to do so due to work constraints.

[madhan]

I fixed the "check for new version" links.
Its checked in into 0.9.5

[Vadim]

If all don't mind we will publish 0.9.5 this week. So, I vote to publish release. Nikolay, elliswr and madhan, what is yours conclusion?

[Nikolay]

Hi Everybody,

It's seems stable.
I'll check again tonight, then will check translations.

[elliswr]

Let's do it.

[madhan]

It does look stable.

[Nikolay]

All translation files has been updated. svn 721.
Thanks.

[Vadim]

So, revision 721 is 0.9.5 final
https://moneymanagerex.svn.sourceforge. ... ases/0.9.5
Now we should build mmex for different OS and upload binaries on sourceforge.

I built Ansi and Unicode setups for Windows, but I don't know how to upload them to sourceforge (or I don't have rights to do that).

[madhan]

Binaries will be hosted here at codelathe.com site, please send me the binaries after building directly to me. I will update the new release in the site.

[madhan]

Release is going up. Windows is done. Mac PPC is done. I need Intel and builds for Linux.

[elliswr]

Intel builds will come over next couple days. I have to muck around with new targets to build from branch source again. Sorry for everyone waiting on that.