Re: Ver 4 problem
- Posted by jimcbrown (admin) Nov 15, 2013
- 2722 views
For those needing references like jimcbrown, i refer you to http://openeuphoria.org/forum/m/120769.wc , feel free click "view thread" and scroll up if you want to view the fighting and drama in getting the fix done to that point.
I looked and couldn't find any there. At most, one could say that it took Matt a few tries to understand that there was still a new leak.
The fixes you describe were indeed done by Feb of 2013, however they won't be in a released version until 4.0.6 is released. http://scm.openeuphoria.org/hg/euphoria/rev/6bae389f572c?revcount=240 http://scm.openeuphoria.org/hg/euphoria/rev/dd834258410e?revcount=240
They are also being documented in the release notes for 4.0.6 (rather than 4.0.5). http://scm.openeuphoria.org/hg/euphoria/file/e79275ac5d37/docs/release/4.0.6.txt
The version you are running is technically a pre-alpha 4.0.6 - but it's so pre-alpha that it reports an incorrect version number!
But the official release of Oct 2012 is known to contain bugs. Why be still releasing it as the current version?! This is infuriating to me,
There was all sorts of addition things that had to happen (such as regression testing and documentation updates) which is why the Feb 2013 version didn't immediately become a new release.
But this is a moot point, as we're ready to release 4.0.6 and 4.1.0 now.
and at least annoying to Ry (as he started that thread about it a week ago, which was never fully answered by any devs).
Well, Ry is a dev, so I suggest you take up the full answer with him.
It's infuriating to me because it's as if you are shooting yourself in both feet as to Eu being seen as bugfree and stable, and some of us know you're doing it, and there's nothing we can do about it but complain on the forum like this.
Again, Ry is a dev, he can do the entire release by himself if he wanted to. There's nothing (that I know of) stopping him.
The Feb 2013 should be the newest release, in my opinion, unless you are hiding something better.
We do have something better, and we're not hiding it. That's the head of the 4.0 branch, which is ready to become the 4.0.6 release.
