Re: [Oorexx-devel] Thinking about a next release ...

[Rick M. <obj...@gm...>]

On Tue, Jul 10, 2012 at 11:50 AM, Mark Miesfeld <mie...@gm...> 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 think those 2 extensions would make a good
> base for a next release.
>
> >From watching the svn notices, I see a lot done with XMl, but I don't
> have any sense of how much work still needs to be done there.
Quite a bit of work left to be honest.  Still working my way through
the various w3c specs making sure I've got good coverage, and there's
a ton of tests that still need to be written, plus a big pile of
documentation.

>
> Coupled with this are two other things I'd like to do.  1.) I'd like
> to not go so long between releases, especially when we have some fixed
> bugs.  2.) I'd like to do releases of some of the extensions
> independent of the interpreter releases.
>
> So, I thought maybe we could kick it around a little and see what
> makes sense to do going forward.  I see 3 possibilities for the
> ooDialog release I want to do:
>
> 1.) Put the current ooDialog stuff that is ready in the 4.1 fixes
> branch.  Do a bug fix + ooDialog release with a beta starting in
> August.

Some of the stuff I've added to the trunk version is currently in a
bit of a half-baked state.  It's sort of the basis for implementing
catch/finally blocks ala NetRexx, but there's a lot more work needed
to take the next step.  The trunk version could be used as a basis,
but there are a few features that probably  need to be buried under
the covers in order for it to go out.

Even if you base this on the 4.1 branch, it probably should be labeled
the 4.2.0 release, with trunk then getting pushed to 4.3

If we're going to base this on the 4.1 branch, we should make a new
4.2 branch from that to use as the working version for the beta and
keep the 4.1 branch just for bug fixes for 4.1

>
> 2.) Do a release with ooDialog and XML as major enhancements.  Start a
> beta around August if that's practical with the XML stuff.

I don't see August as a practical date for the XML stuff being ready.
At this point, I'm not even sure if January is practical, given the
amount of work still required.

However, I've opened quite a few small RFEs recently based on things
that have annoyed me while writing the XML support.  I've just been
opening those with the intent of returning to them once I've going the
XML support a little further along.  I could re-prioritize and see if
I can knock off some of these.  Most of these would be simple to
implement (probably harder to write the tests and docs than the actual
code).  Maybe set a deadline of September.  I'd actually like to use a
few of those for the XML code, even though it means it would be tied
to 4.2.0 release.  Since it already uses 4.1-specific features, I
guess that's not that big of a deal.

>
> 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 ooRexx installation.

I'm comfortable with that too.

Rick

> Liked to hear what people think.
>
> --
> Mark Miesfeld
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Oorexx-devel mailing list
> Oor...@li...
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel