There is a problem with the compatibility between version 2.1 and version 2.0.
"Edit" mode in version 2.0 works like "edit_defaults" custom portlet mode. So, people with Jetspeed 2.0 have important use case: the admin configures portlets on public portal pages for all users (include guests). But Jetspeed 2.1 has user specific preferences. So, when company changes its site from Jetspeed 2.0 to Jetspeed 2.1, all portlets will be with empty preferences (for all users and guests). So, what can company do with site written with Jetspeed 2.0 to succesfully migrate to Jetspeed 2.1?
In preparing for the 2.1 release, could committers please review your
JIRA issues and defer any issues that won't make 2.1
I will be deferring the following issues to the "next" release from
my issue list:
https://issues.apache.org/jira/browse/JS2-560
https://issues.apache.org/jira/browse/JS2-562
https://issues.apache.org/jira/browse/JS2-621
https://issues.apache.org/jira/browse/JS2-622
https://issues.apache.org/jira/browse/JS2-510
I would like to propose that the next version is 2.2
If no one objects, I will create a new 2.2-dev version in JIRA
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
