-----------------------------------------------------------
This mail is generated automatically using
Jakarta Ant. Contents are automatically
downloaded from Apache's Bugzilla.
-----------------------------------------------------------
Please do not reply to this mail.
-----------------------------------------------------------
***********************************************************
COCOON PATCH QUEUE UPDATE
patches in queue: 10
***********************************************************
-----------------------------------------------------------
7507:[PATCH] esql - support CLOB in get-xml
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7507
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: NEW
-----------------------------------------------------------
8509:[PATCH] Allow actions within cocoon views
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8509
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: NEW
-----------------------------------------------------------
8555:[PATCH] Failed to load iso8859-1 displayed on console
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8555
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: NEW
-----------------------------------------------------------
8556:[PATCH] Multiple entries selected in documentation start pag
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8556
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: NEW
-----------------------------------------------------------
8557:[PATCH] null attribute for <esql:get-columns/> and <esql:get
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8557
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: NEW
-----------------------------------------------------------
8614:[PATCH] configurable component manager
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8614
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: NEW
-----------------------------------------------------------
6879:[PATCH] Cache improvement using ESI invalidation protocol
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6879
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: NEW
-----------------------------------------------------------
7187:[PATCH] esql:group, footer fix
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7187
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: NEW
-----------------------------------------------------------
7868:[PATCH] protected createCocoon() in CocoonServlet
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7868
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: REOP
-----------------------------------------------------------
8531:[PATCH] to DirectoryGenerator and Doc
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8531
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: REOP
*************************that's it!************************
------------------------patch HOWTO------------------------
Send patches to http://nagoya.apache.org/bugzilla/
specifying [PATCH] in the summary.
Bugzilla sends a mail automatically to this list.
Reviewers will mark it FIXED there when applied.
Patches not sent to Bugzilla will not be reviewed.
-----------------------------------------------------------
This file is scheduled to be generated every Tuesday and
Friday 1:00 CET for the cocoon-dev mailing list, on
Sundays 1:00 CET for the cocoon-users mailing list.
For any problem, question or suggestion, please notify
[EMAIL PROTECTED]
-----------------------------------------------------------
There is a HEAD branch and sometimes a previous-version
branch that are maintained. Where will the patch go?
1. If it is a bug fix it should go to both branches
2. If something is totally new it goes into HEAD scratchpad.
3. Something in between, but does not break backward
compatibility _may_ go into both (and may not)
4. For everything else, a vote is required so
first it may go into HEAD, and then be VOTEd in order
to sync this into branch.
Please note that structural changes have to be VOTEd first.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
