Re: [Oorexx-devel] Question concerning the (in progress) 3.3 Work

[Gil B. <gi...@be...>]

It occurs to me that if release 3.3 is going to have significant 
structural differences, at least internally, so that a script that has 
been tokenized with 3.2 will not be executable, we should think about 
calling the release 4.0.  This would highlight to our user base that 
they need to be sure that installing the new release does not 
significantly impact their current operations.  To me, a release name 
like 3.3 indicates minor fixes and enhancements and would surprise me if 
an existing working script that happened to be tokenized should fail to 
execute.  I might be more inclined to do some investigation before 
dropping in the new release if it had a name like 4.0.  Just my two 
cents...

Lee Peedin wrote:
> OK,
> That what the "tasks" appeared to be doing - paving the way.  Just wasn't sure if this was the 
> intent of the 3.3 release.  Trying to plan ahead such that the ooRexx Development Team has access 
> via the RexxLA to a 64 bit machine when the time comes. :-)
> 
> Lee
> 
> Rick McGuire wrote:
> 
>>Not likely, but it will be closer.  One of the biggest issues with 
>>making a full 64-bit version was the portability of the APIs.  I'm not 
>>sure we'll be able to get all of that in place for a 3.3 release without 
>>stretching the release out longer than we should.  I'd like to keep with 
>>a release early and often philosophy, so in about 6 months we should 
>>have another major release.  That release is going to be heavy on 
>>internal changes and light on new function, but it will set the stage 
>>for a full 64-bit capable release.
>>
>>Rick
>>
>>On 10/31/07, *Lee Peedin* <le...@sa... 
>><mailto:le...@sa...>> wrote:
>>
>>    Since many of the planned features of 4.0 are being made to the 3.3
>>    release, will the 3.3 release be
>>    64 bit?
>>
>>    Lee
>>
>>    -------------------------------------------------------------------------
>>    This SF.net email is sponsored by: Splunk Inc.
>>    Still grepping through log files to find problems?  Stop.
>>    Now Search log events and configuration files using AJAX and a browser.
>>    Download your FREE copy of Splunk now >> http://get.splunk.com/
>>    <http://get.splunk.com/>
>>    _______________________________________________
>>    Oorexx-devel mailing list
>>    Oor...@li...
>>    <mailto:Oor...@li...>
>>    https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>>
>>
>>------------------------------------------------------------------------
>>
>>-------------------------------------------------------------------------
>>This SF.net email is sponsored by: Splunk Inc.
>>Still grepping through log files to find problems?  Stop.
>>Now Search log events and configuration files using AJAX and a browser.
>>Download your FREE copy of Splunk now >> http://get.splunk.com/
>>
>>
>>------------------------------------------------------------------------
>>
>>_______________________________________________
>>Oorexx-devel mailing list
>>Oor...@li...
>>https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Oorexx-devel mailing list
> Oor...@li...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> 
> 

-- 
Gil Barmwater