David H. DeWolf wrote:
We are down to three remaining issues marked as needed for 1.1.0. I'd
like your comments as to whether you think they should hold up the
release or not.
Current Open Issues:
-----------------------
1) Update version numbers via maven (would be nice, but I may bump it to
1.1.1). Elliot, please comment.
Working on testing this now. I'm committing some of the code to trunk
tonight, and then immediately will attempt to test it by creating a
distribution, then running the pluto testsuite.
If my testing fails I will revert the changes in trunk tonight.
Elliot
David
[EMAIL PROTECTED] wrote:
Thank you, David, for working through all the Jira issues you have for
the past few days. It seems that Pluto 1.1 GA is in our sights.
But, from a users standpoint, I'm not sure if releasing Pluto 1.1
without page layout or preferences persistence is such a good thing.
It seems to be a step back from Pluto 1.0.1 which has both of those
features. Again, I'm thinking about our users, who seem to largely use
Pluto for portlet development. Imagine having to reset your page
layout and preferences every time you have to restart the server while
you are developing a portlet. That would be a real drag. They might
not think the upgrade is worth it.
It might be too late to do a simple preference persistence
implementation (file based?) for Pluto 1.1 GA, but we might want to
shoot for some sort of file persistence of the page layout stuff you
created which simplifies the publishing process. We also need to make
sure the maven and ant deployments work too (see PLUTO-257).
Finally, we should look at the remaining outstanding Jira issues.
PLUTO-234 particularly troubles me since it is the only testsuite test
that fails. I will try to look at this and others as time allows.
That's all I can think of right now. Please add your thoughts on this
issue.
/Craig
