-----------------------------------------------------------
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
***********************************************************
-----------------------------------------------------------
6740:[PATCH] Problem with SOAP Logicsheet in accessing .Net Web S
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6740
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
-----------------------------------------------------------
7184:[PATCH] no sample for esql:group in esql.xsp
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7184
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
-----------------------------------------------------------
7251:[PATCH] XConfTool root node check
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7251
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: NEW
-----------------------------------------------------------
7253:[PATCH] I18nTransformer, adds support for setting translatio
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7253
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: NEW
-----------------------------------------------------------
7328:[PATCH] Minor changes to User docs menu
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7328
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: NEW
-----------------------------------------------------------
7418:[PATCH] *Fast* Java API for Schematron Validation
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7418
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: NEW
-----------------------------------------------------------
6661:[PATCH]LinkStatusGenerator contribution
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6661
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: NEW
-----------------------------------------------------------
6654:[PATCH] Getting Cocoon-2.0.1 working on BES 5
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6654
REVIEWER: [EMAIL PROTECTED]
RESOLUTION:
STATUS: ASSI
*************************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]
