Hans and Jacques:
up till now the rule expressed is
dig in yourself or hire someone familiar enough to do the upgrade.
what I am proposing is that when new "improvements" overwrite existing
code, that a migration plan be developed with scripts.
we now have a patches folder that could be used along with the scripts.
the Goal is to have as much of the migration be automated so a developer
like my self would be able to have confidence his customization are
inline with the "Improvement"
The Migration code would walk through the component-load.xml to find
customizations and see if it relates to the changes of the migration.
The migration should at least say that the customization found is
effected by the changes and show what is effected in the customization,
if it can not actually modify the code.
Also Test Cases for the "improvements" which includes Selenium for UIs
be part of the "Improvement"
Till ofbiz grows into this stature I doubt it will be more than a
Developers playpen.
Hans Bakker sent the following on 9/22/2010 5:37 AM:
Hi BJ,
If you have contributions suitable for the general public, count me in.
I know how you feel, i have the same here too.
Again, create Jira issues with patches and sure, me, Jacques and others
will have a look at it.
Regards,
Hans
