Re: 4.0 vs. 4.1
- Posted by jimcbrown (admin) Nov 03, 2015
- 1426 views
It sounded like you meant something else. I honestly could not believe it. Sorry about that.
Not a problem.
Rather than introduce new changes, I am of the opinion that users prefer to have something that has fewer bugs first. Once squashed, add features.
This was one of the reasons that memstructs was left out of 4.1.0 originally. However, the release of 4.1.0 has taken so long, and apparently for no good reason, that to leave this well developed and well debugged feature out seems like a loss for no gain. (Merging it in wouldn't be very hard and wouldn't take very long, and it seems like more users use the memstructs version instead of the default branch of 4.1, which means it might be better debugged as well.)
Only 4 devs have ever done a release - Jeremy, Matt, Shawn, and Ira (who did 4.1.0 beta). In the past, Jeremy and Matt were the leads and did most of the heavy lifting, but nowadays neither of them appear to have time to do the extremly tedious and unglamourous work involved.
I am under the impression that all of the 4.0 bugs tickets also affect the current 4.1 tip.
To the best of my knowledge, this is correct.
Then the changes ported if necessary to 64-bit platforms.
This is not automatic, however. It's quite possible the author of the 4.0 patch doesn't know how to apply it to 64bit code, and the merger doesn't understand the patch well enough to do the job.
Still, with two main lines and the extra platforms on the 4.1 line, that's probably the best we can do.
