Hello,
OK, I will provide the new 4.1.2 builds, but I have to go on a business
trip to Sao Paulo in a couple of days.
I'll be back 2012-09-15.
Maybe I can squeeze in the build in the next couple of days, but this
would be very tight.
If this does not work out I'll provide the packages as soon as
As we discussed in this thread, I'd like to do releases more often. 3
times a year for bug fixes, assuming we have fixed bugs.
We have a number of fixed bugs now, so I think an August release of 4.1.2
is justified.
I'll get 4.1.2 started this weekend, with a goal of the final release at
the end
René,
My fault. I'll try to get on board with 4.1.2.
Bruce Skelly
On Aug 3, 2012, at 8:15 AM, rvjansen wrote:
Mark,
I think that is a very good idea. We also should try to have the
packages for the different platforms built and available on the same
date.
I was wondering why the
On Fri, Aug 3, 2012 at 8:15 AM, rvjansen rvjan...@xs4all.nl wrote:
I think that is a very good idea. We also should try to have the
packages for the different platforms built and available on the same
date.
I was wondering why the MacOSX installers did not end up at the
ooRexx.org site/SF
Hi All,
Thinking ahead to the next release ...
I've finally finished up with everything I wanted for ooDialog, so it
is ready to go into a regular beta / release cycle. In addition, Rick
has done a lot with XML. I think those 2 extensions would make a good
base for a next release.
From
On Tue, Jul 10, 2012 at 11:50 AM, Mark Miesfeld miesf...@gmail.com wrote:
Hi All,
Thinking ahead to the next release ...
I've finally finished up with everything I wanted for ooDialog, so it
is ready to go into a regular beta / release cycle. In addition, Rick
has done a lot with XML. I
It depends, Mark.
Does the new ooDialog have any backward compatibility issues? Will
anyone have to touch any of their existing ooDialog routines just
because they need a particular bugfix in ooRexx?
If so, option 3 is preferable. Keep them separate, so a user can get
the latest bugfixes
On Tue, Jul 10, 2012 at 9:10 AM, Rick McGuire object.r...@gmail.com wrote:
On Tue, Jul 10, 2012 at 11:50 AM, Mark Miesfeld miesf...@gmail.com wrote:
Hi All,
Thinking ahead to the next release ...
1.) Put the current ooDialog stuff that is ready in the 4.1 fixes
branch. Do a bug fix +
On Tue, Jul 10, 2012 at 9:44 AM, Rick McGuire object.r...@gmail.com wrote:
On Tue, Jul 10, 2012 at 12:35 PM, Mark Miesfeld miesf...@gmail.com wrote:
3.) I can do an ooDialog only beta / release independent of the
interpreter. ooDialog would have an installer that drops it into any
4.1.0
On Tue, Jul 10, 2012 at 12:52 PM, Mark Miesfeld miesf...@gmail.com wrote:
On Tue, Jul 10, 2012 at 9:44 AM, Rick McGuire object.r...@gmail.com wrote:
On Tue, Jul 10, 2012 at 12:35 PM, Mark Miesfeld miesf...@gmail.com wrote:
3.) I can do an ooDialog only beta / release independent of the
On Tue, Jul 10, 2012 at 9:25 AM, Chip Davis c...@aviatrexx.com wrote:
Does the new ooDialog have any backward compatibility issues?
That's the big question. I've tried very hard to not break backward
compatibility. But ...
There are 2 areas. One is that there are a few methods that in the
I know we sort of promised that the next release would be devoted to
implementing the replacement for the orxscript support, but the more I
look at doing this, the less I feel motivated to spend the time trying
to fix this. I frankly am a bit exhausted by the 4.0 release, and I
would like to
On Sun, Jun 28, 2009 at 6:55 AM, Rick McGuireobject.r...@gmail.com wrote:
I know we sort of promised that the next release would be devoted to
implementing the replacement for the orxscript support, but the more I
look at doing this, the less I feel motivated to spend the time trying
to fix
13 matches
Mail list logo
