OpenEuphoria

Re: suggestion

• Posted by Jeremy Cowgar <jeremy at cowga?.?om> May 13, 2008
• 705 views

jacques deschênes wrote:
> 
> I suggest that we the trace the line for the next version. If we always add
> new features, we'll never see the end of it.
> 
> here how I see it.
> 
> 1) before any work on a new version: discuss improvements
> 2) agree on which ones will be included in next version.
> 3) trace the line.
> 4) start working on next version
> 5) queue any further suggestions for after next version.
> 6) release next version
> 7) goto to step 1
> 

It's always good to have a plan yes. I created a roadmap on the wiki a while
ago: http://euwiki.ayo.biz/Roadmap however, I have been stalling for some
decisions to be made.

In stalling, I started a doc overhaul which CK Lester is working on (and could
use some help). During this time, I have spent time in the interpreter and
translator code learning it. In learning, I found a few things I could do. I
closed some bugs, saw some old feature requests out there, so I began posting
here for discussion as to see which features should be implemented or not.

The big thing to me that needs done is more improvements of the namespace.
That's of the utmost priority but we are not totally sure what to do there yet to
solve some name conflicts. That's another thing that put me in a holding pattern.

SF.net has a feature request list:
http://sourceforge.net/tracker/?group_id=182827&atid=902785

The wiki also has a feature request list (some of which I've implemented):
http://euwiki.ayo.biz/Category:Requested_functionalities

I think we should focus on things that will possibly break code as 4.0 does have
a few of those in it. If we are going to break code, I think we should have one
release that breaks code, not one release that breaks a little code (4.0), then
have 4.1 break a little more, 4.2 break a little more, etc... (well, actually, I
think within major versions, code should not be broken). Breaking code should not
be a repetitive thing.

Your right. A list needs to be created.

Now, how to go about creating this list?

--
Jeremy Cowgar
http://jeremy.cowgar.com