uPortal developers,
A client [1] has been generous enough to throw me a few [2] hours to
work on ALM diagnostics, error detection, and bugfixing, with an
especial need to apply these changes to 2.4.2. I'd like to create a
"2-4-2-alm-maint" exploratory branch for the purpose of sharing this
maintenance code. I hope this will be of interest and use to fewer and
fewer uPortals as folks migrate to DLM, but since this is maintenance of
uPortal itself it seems to me to belong in uPortal source control.
Andrew
[1]: I dislike that cloak and dagger "some client, somewhere" allusion
probably even more than you do, and I'll see about giving credit where
credit is due on any fruits of this labor. More openness is better.
Unfortunately, it's not always clear how much it is acceptable to share
when.
[2]: Don't expect the realization of all ALM hopes and dreams ever had
out of this effort -- it's a very few hours involved. However, with a
maintenance branch to explore mitigating issues in ALM in older uPortal
environments, there's a place for continued collaboration on this if
desired.
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
