Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

ooRexx 4.1.1 Is Now Available

19 views
Skip to first unread message

Mark Miesfeld

unread,
May 28, 2012, 1:03:18 AM5/28/12
to
The Open Object Rexx Development Team is proud to announce the
availability of ooRexx 4.1.1. This is a bug fix only release, with 35
to 40 bugs fixed.

The Windows and Linux versions of ooRexx are available immediately on
SourceForge. You can download ooRexx 4.1.1 from

http://sourceforge.net/projects/oorexx/files/oorexx/4.1.1/

The documentation has not as yet been put on SourceForge. It will be
uploaded in the next few days to be available at

http://sourceforge.net/projects/oorexx/files/oorexx-docs/4.1.1/


Download the CHANGES document, in the ooRex files area, to see the
list of fixes. The readme.pdf file contains additional information
concerning the release.

If you discover bugs please open a bug report at

http://sourceforge.net/tracker/?group_id=119701&atid=684730

The ooRexx Development Team

Swifty

unread,
May 28, 2012, 3:05:02 AM5/28/12
to
On Sun, 27 May 2012 22:03:18 -0700 (PDT), Mark Miesfeld
<mies...@gmail.com> wrote:

>This is a bug fix only release, with 35
>to 40 bugs fixed.

My REXX says it is 4.1.1 from Feb 26, so a late beta or an RC.

To work out the value of moving to 4.1.1 GA I'd need to know what
release I'm currently on, then find a list of bugs fixed between those
two releases.

Is this possible?

I'm in the process of teaching myself SVN. If your repository is SVN
compatible, I could try to find my own answer; it would be an
interesting learning exercise.

--
Steve Swift
http://www.swiftys.org.uk/swifty.html
http://www.ringers.org.uk

Mark Miesfeld

unread,
Jun 8, 2012, 10:50:35 AM6/8/12
to
On May 28, 12:05 am, Swifty <steve.j.sw...@gmail.com> wrote:
> On Sun, 27 May 2012 22:03:18 -0700 (PDT), Mark Miesfeld
>
> <miesf...@gmail.com> wrote:
> >This is a bug fix only release, with 35
> >to 40 bugs fixed.
>
> My REXX says it is 4.1.1 from Feb 26, so a late beta or an RC.
>
> To work out the value of moving to 4.1.1 GA I'd need to know what
> release I'm currently on, then find a list of bugs fixed between those
> two releases.
>
> Is this possible?

It is certainly possible, the ooRexx source code repository is a
subversion (svn) repository. Use your svn client to check out the
4.1.1 release branch. The svn URL for check out is:

https://oorexx.svn.sourceforge.net/svnroot/oorexx/main/releases/4.1.1/trunk

Once checked out, go to the root of the source tree and execute: svn
log

You get a log output like this:

C:\work.ooRexx\wc\main.4.1.1.release>svn log | more
------------------------------------------------------------------------
r7795 | miesfeld | 2012-05-16 08:26:45 -0700 (Wed, 16 May 2012) | 1
line

Move ooRexx 4.1.1 files to relase tree
------------------------------------------------------------------------
r7691 | wdashley | 2012-03-20 09:40:19 -0700 (Tue, 20 Mar 2012) | 2
lines

Fix rpm spec file so that Rexx applications can be linked once ooRexx
has been installed.

------------------------------------------------------------------------
r7679 | miesfeld | 2012-03-16 07:14:04 -0700 (Fri, 16 Mar 2012) | 1
line

Update the fixed bug list for 4.1.1
------------------------------------------------------------------------
r7678 | miesfeld | 2012-03-16 07:09:21 -0700 (Fri, 16 Mar 2012) | 1
line

3506001 ListChoice fails if 16 items passed
------------------------------------------------------------------------
r7670 | bigrixx | 2012-03-15 03:22:19 -0700 (Thu, 15 Mar 2012) | 1
line

Fix failure in lines()
------------------------------------------------------------------------
r7663 | bigrixx | 2012-03-14 06:46:33 -0700 (Wed, 14 Mar 2012) | 1
line

fix default return value problem
------------------------------------------------------------------------
r7653 | miesfeld | 2012-03-12 18:01:20 -0700 (Mon, 12 Mar 2012) | 1
line

Update the fixed bugs list in the 4.1 fixes branch
------------------------------------------------------------------------
r7652 | miesfeld | 2012-03-12 17:47:30 -0700 (Mon, 12 Mar 2012) | 1
line

2933987 two rxapi.exe tasks - don't start rxapi if it is already
running
------------------------------------------------------------------------
r7642 | bigrixx | 2012-03-10 13:45:27 -0800 (Sat, 10 Mar 2012) | 1
line

[ oorexx-Bugs-3501117 ] Crash at end of program

...


The "Move ooRexx 4.1.1 files to relase tree" line shows exactly when
the beta / rc was converted to the release.

The active developers generally commit a bug fix, fix, as a single
commit and mark it. This is a convention, not a strict rule. But you
can pretty much count on it. So you see that Rick commited a bug fix
on 3/10 (oorexx-Bugs-3501117) and I commited a bug fix on 3/12
(2933987 two rxapi.exe tasks) The bug number lets you look up exactly
what the bug was.


> I'm in the process of teaching myself SVN. If your repository is SVN
> compatible, I could try to find my own answer; it would be an
> interesting learning exercise.

Go for it. The next thing you know you'll be checking out trunk and
doing your own builds.

--
Mark Miesfeld

Swifty

unread,
Jun 9, 2012, 3:11:42 AM6/9/12
to
On Fri, 8 Jun 2012 07:50:35 -0700 (PDT), Mark Miesfeld
<mies...@gmail.com> wrote:

>Go for it. The next thing you know you'll be checking out trunk and
>doing your own builds.

I'm still working on hello.c so some way to go yet. Thanks!

U.Zinngrebe

unread,
Jun 9, 2012, 11:49:12 AM6/9/12
to
Swifty wrote:

> On Fri, 8 Jun 2012 07:50:35 -0700 (PDT), Mark Miesfeld
> <mies...@gmail.com> wrote:
>
>>Go for it. The next thing you know you'll be checking out trunk and
>>doing your own builds.
>
> I'm still working on hello.c so some way to go yet. Thanks!
>

Go for it. It is much easier than it seems.

The five commands below should provide your own rpm.

Cheers, Uli

(who gave up working on hello.c)




svn co https://oorexx.svn.sourceforge.net/svnroot/oorexx/main/trunk ~/oorexx

cd ~/oorexx/main/trunk

./bootstrap

./configure --disable-static

make rpm
0 new messages