cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicola Ken Barozzi" <baro...@nicolaken.com>
Subject [PATCH QUEUE] Summary 14-12-2001
Date Fri, 14 Dec 2001 16:53:28 GMT
***********************************************************
             __   __   __   __   __   __
            (___ (__) (___ (__) (__) |  )

           __   __  _|_   __  |__   ___    __
          |__) (__(  |_, (___ |  ) (__/_ __)
          |
***********************************************************
*****************  patches in queue: 4 ********************
***********************************************************
-----------------------------------------------------------
Please 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.
***********************************************************
This file is updated regularly at least once a week.
If you don't find the patch you submitted (before) in
this list, please notify xml-cocoon@nicolaken.com
-----------------------------------------------------------
There is usually a HEAD branch and 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 (like DBXML: protocol or
    Lucene search) 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.
***********************************************************

-----------------------------------------------------------
[patch] SectionCutter Action
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4289

DATE:       19-10-2001
AUTHOR(S):  sergio.carvalho@acm.org (Sergio Carvalho)
REVIEWER:   nobody
APPLIES TO: HEAD

-----------------------------------------------------------
[patch] New actions for Cocoon 2
-----------------------------------------------------------
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4287

DATE:       19-10-2001
AUTHOR(S):  paolo@arsenio.net (Paolo Scaffardi)
REVIEWER:   nobody
APPLIES TO: HEAD

-----------------------------------------------------------
[PATCH] XSLT file locking in Cocoon 2
-----------------------------------------------------------
DATE:       14-12-2001
AUTHOR(S):  (mhartle@hartle-klug.com) Michael Hartle
REVIEWER:   nobody
APPLIED TO: 2+

-----------------------------------------------------------
[PATCH] pretty-content view in sitemap.xmap
-----------------------------------------------------------
DATE:       14-12-2001
AUTHOR(S):  xml-cocoon@nicolaken.com (Nicola Ken Barozzi)
REVIEWER:   unassigned
APPLIES TO: HEAD


***********************************************************
****************  applied this week :1 ********************
***********************************************************

-----------------------------------------------------------
[PATCH] main stylesheets to look ok in Mozilla too
-----------------------------------------------------------
DATE:       13-12-2001
AUTHOR(S):  Nicola Ken Barozzi <barozzi@nicolaken.com>
REVIEWER:   Gerhard Froehlich <g-froehlich@gmx.de>
APPLIED TO: 2+

***********************************************************

-----------------------------------------------------------
[PATCH] Template
-----------------------------------------------------------
DATE:       dd-mm-200y
AUTHOR(S):  Name email
REVIEWER:   nobody
APPLIED TO: all

*************************that's it!************************

Carsten Ziegeler wrote:
> Hi Nicola,
>
> thanks for your offer to post/maintain this summary! I really honor
> it, if you will spent your time on this!
>
> But I think, this could be done somehow automatically. Some
> time ago, we searched for a way to cope all the patches comming
> in. As a ad hoc solution, bugzilla was suggested, so a
> submitter could add an entry to bugzilla with the key word
> patch.
> So, first thing would be to include those patches already
> listed in bugzilla in your list and then we should find a solution
> to make this automatically. One possibility is to add all outstanding
> patches into bugzilla and generate reports every week or so (I hope
> this is possible).

In the meantime I'm here :-)

Nicola Ken Barozzi These are the days of miracle and wonder...
                                ...so don't cry baby, don't cry
<xml-cocoon@nicolaken.com>                          Paul Simon


> > -----Original Message-----
> > From: Nicola Ken Barozzi [mailto:barozzi@nicolaken.com]
> > Sent: Thursday, December 13, 2001 11:11 PM
> > To: cocoon-dev@xml.apache.org
> > Subject: [PATCH QUEUE] Summary
> >
> >
> > me:
> > > To make everyone in the list see that patches submitted are in the
queue
> > and
> > > not forgotten, I would like to start from today to send a mail
> > to the list
> > > with currently open patches.
> > > If you don't agree, please -1 on it and I will not start.
> > > Well, let's see if I can help on this... and how much I will resist
;-)
> >



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message