1. Release questions

Here are some questions I'd like to answer before releasing 4.1:

  • should we merge the memstruct or jsmn branches?
  • are there any blocking bugs or incomplete features?
  • should we release 4.0.6 as well?

This is all I have for now but there are more stewing in the back of my brain.

Here are some relevant threads from the past few years, regarding releases:

Date Subject
Jan 13, 2015 OpenEuphoria's Strategy
Feb 02, 2015 Happy Birthday to Euphoria 4.1.0
Feb 02, 2015 "Fixed" bug
Feb 03, 2015 Packaging and Eubins
Nov 03, 2015 4.0 vs. 4.1
Mar 10, 2016 Committee for the 4.1.0 Release Candidate

-Greg

new topic     » topic index » view message » categorize

2. Re: Release questions

ghaberek said...

Here are some questions I'd like to answer before releasing 4.1:

  • should we merge the memstruct or jsmn branches?
  • are there any blocking bugs or incomplete features?

This is all I have for now but there are more stewing in the back of my brain.

Here are some relevant threads from the past few years, regarding releases:

Date Subject
Jan 13, 2015 OpenEuphoria's Strategy
Feb 02, 2015 Happy Birthday to Euphoria 4.1.0
Feb 02, 2015 "Fixed" bug
Feb 03, 2015 Packaging and Eubins
Nov 03, 2015 4.0 vs. 4.1
Mar 10, 2016 Committee for the 4.1.0 Release Candidate

-Greg

I think merging the memstruct branch would be a good idea. Also, is a new release of Euphoria coming soon?

new topic     » goto parent     » topic index » view message » categorize

3. Re: Release questions

Icy_Viking said...

I think merging the memstruct branch would be a good idea. Also, is a new release of Euphoria coming soon?

Yes, I am trying. God help me, I'm trying.

http://openeuphoria.org/forum/132342.wc

-Greg

new topic     » goto parent     » topic index » view message » categorize

4. Re: Release questions

There are unit tests results now at http://openeuphoria.org/wiki/edit/EuphoriaDevelopment.wc . Even in 4.0, there are problems.

new topic     » goto parent     » topic index » view message » categorize

5. Re: Release questions

SDPringle said...

Even in 4.0, there are problems.

That raises another question I meant to add: should we release 4.0.6 as well? I would say no.

-Greg

new topic     » goto parent     » topic index » view message » categorize

6. Re: Release questions

What exactly is test/t_abadcase.e supposed to do? It doens't run well on Windows and in fact, hangs indefinitely until I kill the process.

-Greg

new topic     » goto parent     » topic index » view message » categorize

7. Re: Release questions

It is a test for this fix. http://scm.openeuphoria.org/hg/euphoria/rev/77461ca5af3a Which is a fix for this bug. http://openeuphoria.org/ticket/944.wc Which is a bug for this report. http://openeuphoria.org/forum/129577.wc#129577 The bug, and the test, are only designed to run on Linux. It seems the author of the test case could not come up with a simpler version that reproduced the bug. The bug itself is in the very last lines of the test, where case else is hit even though l3 is 1.

new topic     » goto parent     » topic index » view message » categorize

8. Re: Release questions

Releasing is just running a bunch of scripts, really. Which sounds really easy. The hard part is having everything installed and all of the platform-chip combinations for building binaries. Once you have all of that, 4.0.6 is easy.

There were three unit-test file failures in 4.0. One was due to a constant introduced in a certain file. This file is used to create the warning list used by one of the test files. Because this constant was introduced a warning was added to a list that was not accounted for in the test. So, it wasn't a real failure just a test file that wasn't updated. I doubt the t_net_http is a real failure either.

I suspect the server the t_net_http test uses is just not returning the right values in which case we can fix this server or the test file itself.

That would leave just one to go. We can still use 4.0 as the place to put common bug fixes whether not we never release anything from it. For me, Greg has apparently solved the problem for getting 4.1 working on 64-bit. I'm sorry if I sound apathetic.

new topic     » goto parent     » topic index » view message » categorize

9. Re: Release questions

ghaberek said...

What exactly is test/t_abadcase.e supposed to do? It doens't run well on Windows and in fact, hangs indefinitely until I kill the process.

-Greg

It was I who wrote that test. I spent a long time trying to shorten it and it still is longer than a baby's arm.

If it is hanging on Windows, it looks like there is a regression in the Windows build. Maybe you should run trace and trace through the program to see if there is an non-terminating loop. Perhaps the platform difference is enough to prevent a loop from terminating.

Trying to port this test to Windows without a copy of a version that triggers the bug is pointless. If you change anything, there is no way to tell if the test would work to find the old bug. You could backout of the bug-fix change and see if you trigger the bug. If you go through this, you can at least verify that the test still works. Changes should result in one where the test fails on the backed out version of Euphoria but passes on the current version of Euphoria.

new topic     » goto parent     » topic index » view message » categorize

10. Re: Release questions

Are you going to look at adding tail recursion again? It was removed; http://openeuphoria.org/ticket/935.wc

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu