[+] Create rc1 on Sunday
I'm very much in favor of going to RC level ASAP!
The only reservation I have is that I'd like to add a minor enhancement to the
portlet support with respect to the handling of header contributions.
Right now, header contributions are embedded inline in a portal page, resulting in potentially duplicated header inclusions (e.g. javascript/css) if multiple
wicket portlets are present on that page.
So far this isn't a big technical issue but ugly nonetheless.
The *optional* enhancement I have in mind will allow native integration with
existing portals support for merging header contributions (like Jetspeed
provides).
This will also be inline with the JSR-286 Portlet API 2.0, so I'd very much
would like to add that before the final 1.3.0 release.
But, as I will depend on a new (pre-JSR-286) interface provided by Apache Portals Bridges for this, I've to wait until the release of Apache Portals Bridges
1.0.4, scheduled for in about 2 weeks time (before ApacheConUS).
I know very well the consequences of going RC level, so this *might* pose a
problem for me, although I don't expect it.
*If* I'm ready to provide such an enhancement, I'll make sure to do it only as an optional feature, and AFAICS won't require real API changes at all and will
only affect the portlet related classes. I definitely will not touch any of the normal core API.
At any rate, all be assured: I won't commit such a change without asking for a
vote on it.
Regards,
Ate
Frank Bille wrote:
Hey all,
I have time to build a release on Sunday. So what's it gonna be? Another
beta release? A release candidate?
IMHO we should go for the release candidate now, so we can get final out the
door before Christmas. Does that sound unreasonable?
[ ] Create beta5 on Sunday
[ ] Create rc1 on Sunday
[ ] Not yet!
Frank
