On Nov 26, 2007, at 2:53 PM, Ron Wheeler wrote:
I may be way off base but as a newbie, I am trying to get my head
around the general problem of how to customize a Jetspeed portal
to meet my needs while at the same time , staying in a position to
move to the next version of Jetspeed.
Every Jetspeed resource that my developers touch will have to be
remembered so that we can merge our modifications into the next
version of Jetspeed.
What resources are you changing that need to be remembered?
If I skip a version of Jetspeed (ie ignore 2.1.3 and probably 2.2
since it is just packaging), it may be difficult to find all of the
things that have to be changed to get my customizations working
again under 2.2.2.
I am wondering how everyone else deals with this. Is there a set of
"Best Practices" for developing with Jetspeed, that is becoming
clear to the Jetspeed community?
Does everyone move to the new versions as they are issued?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
