On 6/5/07, Gerhard Killesreiter <gerhard@killesreiter.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jim Li schrieb:
Hello, first off I apologize if this is inappropriate for this list.
It is more infrastructue related, me thinks.
I just leaned that custom logging (by Kahlid) and JS aggregation (by M3avrck) has been backported to 5.x. So I was thinking does it make sense to have a central repository for all these fine backport/performance patches, which may never land in the official 5.x release?
Will never.
(Or does it already exist?) Another high profile patch I am aware of is the tracker query patch (by David Strauss). There gotta be more, including some of the locally applied to d.o. ones that never got released.
All the patches that are applied to d.o are availabl ein the issue tracker.
I would like to not see these patches mixed in with issues which are on track to go in a stable version. I do not think using the 'patch (code needs review)' or 'patch (ready to be committed)' statuses are appropriate. The best fit I see is 'won't fix.' -- Neil Drumm http://delocalizedham.com