I have completed steps 1 and 4. I would like to work on step 3 next:
Remove from the Mini-language Java code all deprecated items that are
marked in red in the reference.
If there are no objections over the next few days I will begin work on that.
-Adrian
On 4/19/2012 12:09 PM, Adrian Crum
Hi Adrian,
i very much appreciate your work on this. But as you sure expected,
please keep in mind backward compatibility?
Can you also please add some junit tests to check the functionality did
not change?
Regards
Hans
On 04/20/2012 05:37 PM, Adrian Crum wrote:
I have completed steps 1 and
Hans,
Please read the discussions on this subject and the Mini-language
reference page.
The mini-language unit tests are practically non-existent, and I will be
adding them as I go along. Keep in mind that an overhaul means things
will change - that is the whole point of the effort.
Hi Adrian,
Before removal of deprecated minilang functions I would be wise to assess
the implications in current trunk. It would make sense to remove them and
then find out that parts of functionality (in whatever application) doesn't
work any more. With enduser annoyance as a result. And this is
On the other hand, if we include the changes in the upcoming release branch as
Adrian suggests, it may be easier to backport bug fixes from trunk: if trunk
and release12.04 will have different Minilang syntax we will get a lot of
conflicts when backporting patches.
Jacopo
On Apr 15, 2012, at
Yes trunk is the bleeding edge anyway...
Jacques
From: Jacopo Cappellato jacopo.cappell...@hotwaxmedia.com
On the other hand, if we include the changes in the upcoming release branch as Adrian suggests, it may be easier to backport bug
fixes from trunk: if trunk and release12.04 will have
That is correct - if I make the non-functional changes before the
release branch is created, then future trunk fixes will be easier to
backport to the release branch. A separate fix will be needed for
versions prior to 12.x.
-Adrian
On 4/19/2012 7:29 AM, Jacopo Cappellato wrote:
On the
I am still working on the Mini-language Reference page:
https://cwiki.apache.org/confluence/display/OFBADMIN/Mini-language+Reference
but it is taking longer than I expected due to the enormity of the task.
I would like to get some preliminary code changes committed to the
project before the
Wouldn't be better to cut the 12.04 branch and then start the refactoring work
on trunk?
This will remove some workload for backporting bug fixes in the new branch;
then we will have one year to complete the refactoring that will be available
in 13.04; users of 12.04 will have to upgrade all
