1. 4.0 Status
- Posted by jeremy (admin) Mar 18, 2009
- 913 views
I just wanted to update everyone on the status of 4.0. I know it has seemed like a long road, but for the devs it has been all too short! Anyway, most of you know that we are expecting 4.0a3 to be the last alpha release. The next release of Euphoria will be 4.0b1. How quickly we move through the beta stages depends very much so on you! When the beta hits, we need users to test 4.0 as though they have never tested before. This will ensure two things:
- That 4.0 final will be a stable deploy not requiring a rush fix of 4.0.1 3 days later.
- That the beta stages will move swiftly and 4.0 final will come quickly after.
I have posted a few messages here in regards to submitting bug reports that I would like everyone to review and begin to use as a guideline as to how to report a problem, not just with the up coming beta but with the current alpha. This will be vital to our success, and will also cause the devs to be a bit happier at the end of the day as they are not looking under every nook and crannie for bug reports.
We have spoken on the development list and are shooting for a final release in May. The details have not yet been nailed down and it will, again, largely depend on you. Help us as much as you possibly can with the 4.0 release, it is a huge upgrade with a lot of code changes. I was reviewing the SVN logs this morning and over the past 11 months, there has been over 1,200 SVN commits, that's just about 4 commits every single day for the last 11 months! The standard library has had a vast overhaul and has expanded from 178 public symbols to over 600 public symbols, all very nicely organized. Many new features have been added such as namespace enhancements, conditional compilation, forward references, default parameters, decision keywords were added, new scope words, configuration files, new command line arguments to help development and much more. This is going to be a grand deployment.
Once 4.0 final is deployed, the work is not over. Euphoria is here because of two reasons.
- People use it
- Developers develop it
If either of those begin to decrease, Euphoria suffers. If either of those begin to gain, Euphoria benefits. Once 4.0 is deployed, we need to turn out attention to promoting Euphoria. We have created a page on the wiki, How to Promote Euphoria that I hope everone will take to heart. The more people who use it, the more code we have to reuse in The Archive. The more people who use it, the more who will become a Euphoria core developer, which in turn means, the better, the more stable Euphoria will become.
I know this has been noting but rambling, but, I hope you're excited about the upcoming 4.0 release as the devs are.
Jeremy
2. Re: 4.0 Status
- Posted by Kat Mar 18, 2009
- 892 views
- Last edited Mar 19, 2009
You know a really big boost would be if the code in the archives actually worked. Right out of the box. And worked with v4, with all necessary includes actually included in each application's zip file. Perhaps everyone who has contributed might update their contribution, so once unzipped on a stranger's computer, it works 100% without the user needing to ask where this or that missing include is. And maybe "updating" the code to work with Eu v4, which has moved functions and procedures to different files. And yes, i know the V4 distribution has the 3.1 files in it, but it might not keep those older files in it in future releases.
You don't haveto do it. No one is forcing you. Someone is sure to think this is a bad idea. Feel free to listen to them.
useless
3. Re: 4.0 Status
- Posted by mattlewis (admin) Mar 19, 2009
- 849 views
You know a really big boost would be if the code in the archives actually worked. Right out of the box. And worked with v4, with all necessary includes actually included in each application's zip file. Perhaps everyone who has contributed might update their contribution, so once unzipped on a stranger's computer, it works 100% without the user needing to ask where this or that missing include is. And maybe "updating" the code to work with Eu v4, which has moved functions and procedures to different files. And yes, i know the V4 distribution has the 3.1 files in it, but it might not keep those older files in it in future releases.
I fully agree. I've been working on updating my projects to at least work with 4.0, and some are actively using 4.0 features.
Matt
4. Re: 4.0 Status
- Posted by ChrisB (moderator) Mar 19, 2009
- 856 views
Hi
2 points
There ae quite a few projects that no longer have active developers (as far as I am aware), eg exotica and morfitt. These are still useful, but the original developers have left. What does the community think about updating these to be 4 compatible, and resubmitting them to the archive, if we are unable to contact the original contributors?
Next point. If libraries are updated, and become 3.1 unusable, a lot of poeple will be alienated. May I suggest that (for now) libraries are resubmitted in an updated form, that either states clearly that the lib is 3 and for compatible, or 4 only, or has 2 folders within the zip (3.x and 4.x) so that people can use the library they need. Hopefully this should not be much of an issue, because most of the libs I have tested work, those that don't need mostly just namespace resolution.
Chris
5. Re: 4.0 Status
- Posted by jeremy (admin) Mar 19, 2009
- 788 views
I've created a new thread about the archive discussions here, please see: The Archive and 4.0
Jeremy
