-----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.
All these patches (at least the above 3 I mentioned) would be great to have on my existing 5.x sites. But they are buried deep in the issue queue or comment thread, thus easy to miss. My guess is most ppl aren't even aware of them unless they follow issue queue and dev list closely. Can we somehow organize them in a central place, Group, Document page or even a Project? Does it make sense and worth the efforts? Any comments? Thanks.
Frankly, no, to me this does not make sense. Promoting these patches will lead to a support nightmare from 1) people who can't patch to save their lives, but want these patches (and probably don't need them) 2) people who can patch and then forget they did patch when they upgrade. Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGZa2Lfg6TFvELooQRAm5pAKCS/wobJxms0C1k5jIiF+s9XsS+AwCgqLSM AEBRK2YVF3Wib1hgtYslCQ0= =XlPq -----END PGP SIGNATURE-----