1. Committee for the 4.1.0 Release Candidate
- Posted by jimcbrown (admin) Mar 10, 2016
- 1904 views
Forked from Re: UI/IDE committee
Maybe not for March 31, but when OE4.1 is released we will have something valuable.
I wanted to try this next.
Basically, the concensus has been that we've been ready to release 4.1.0 for a while, but nothing much has happened since then.
I think the UI committee did a good job of finding a solution, and then taking steps to implement it. While the committee wasn't able to finish by the deadline,that was because the deadline was completely unreasonable to begin with. Aside from that minor point, it's been a great success.
This being the case, I think having a committee to come up with a 4.1.0 Release Candidate would be a good idea. A new strike team (this time allowed to set their own deadline), prepared to do whatever it takes to get a working release out there, may well work wonders (again).
Any takers?
2. Re: Committee for the 4.1.0 Release Candidate
- Posted by SDPringle Mar 11, 2016
- 1853 views
The problem is that there are two bugs that I would put as blocking. I no longer feel that releases matter because you can install the all in one installer. If releases matter, release 4.0.6. Euphoria 4.1 is not ready.
There are three very important issues with 4.1 (development) :
- sometimes the wrong case is jumped to
- sometimes tail recursion results in wrong c code.
- warnings are not always getting issued when theyare supposed to
The warnings problem also exists in 4.0.6 in my March release.
3. Re: Committee for the 4.1.0 Release Candidate
- Posted by jimcbrown (admin) Mar 11, 2016
- 1761 views
The problem is that there are two bugs that I would put as blocking.
There are three very important issues with 4.1 (development) :
- sometimes the wrong case is jumped to
- sometimes tail recursion results in wrong c code.
- warnings are not always getting issued when theyare supposed to
The warnings problem also exists in 4.0.6 in my March release.
Here are the two 4.1.0 specific tickets. In addition for actually following the steps for issuing a release, I think the committee should form a game plan for dealing with these bugs and fixing them. Alternatively, we could set up a second committee just to take care of the blocking bugs. (You hint that the issue with wrong case appears to be related to a missing NOP related to tail recursion... could these two in fact have the same root cause?)
4. Re: Committee for the 4.1.0 Release Candidate
- Posted by SDPringle Mar 11, 2016
- 1750 views
You hint that the issue with wrong case appears to be related to a missing NOP related to tail recursion..
I think we would have fewer bugs going forward if the byte code language of Euphoria was exactly the same for the interpreter and translator. The test I wrote for this goes to the wrong case when interpreted. NOP is illegal for the interpreter yet obligatory for the trsnslator.
Ticket 935, is caused by an attempt to optimize. If we just make the flag that activates it a constant and remove the activation code the problem should disappear but we will need to remove tail recursion from the docs. Don't forget to update the docs. It is better to be always correct and slower than fast but wrong.
SD Pringle
5. Re: Committee for the 4.1.0 Release Candidate
- Posted by SDPringle Mar 11, 2016
- 1770 views
I recommend those who want to be on a release committee listen to Changelog 197 at 0:41:45 to 0:44:45.
6. Re: Committee for the 4.1.0 Release Candidate
- Posted by jimcbrown (admin) Mar 11, 2016
- 1741 views
I recommend those who want to be on a release committee listen to Changelog 197 at 0:41:45 to 0:44:45.
Where is this / how do I get to it? Do you have a link?
7. Re: Committee for the 4.1.0 Release Candidate
- Posted by SDPringle Mar 11, 2016
- 1788 views
You can get it here. https://changelog.com/podcast/
8. Re: Committee for the 4.1.0 Release Candidate
- Posted by SDPringle Mar 11, 2016
- 1799 views
You can get it here. https://changelog.com/podcast/
9. Re: Committee for the 4.1.0 Release Candidate
- Posted by jimcbrown (admin) Mar 11, 2016
- 1792 views
You can get it here. https://changelog.com/podcast/
Thanks!
