On Fri, Dec 10, 2010 at 3:32 PM, Antonio Petrelli <[email protected]> wrote: > Good question. Take a look at this issue: > https://issues.apache.org/jira/browse/TILES-404 > It is clear that they preferred fixing Tiles in a package built by > them instead of patch official Tiles. The issue has been opened 6 days > after publishing the package. Why?
Same reason any corporate entity would patch it and do an internal release. They need it fixed _now_, not when the volunteer labor force at Apache gets around to accepting the patch and doing a release. :) It's just that their "internal" releases are visible. It's nice that they contribute the fixes back, you don't always get that much. Spring in particular already has their own communities and processes, so not much incentive to come participate here. They're already maintaining a fork, so if the rest of the community would rather work over there, then we can move Apache Tiles to the Attic and everyone can wander over to SpringSource. In the end it all comes down to where the people who are doing the work want to do it. It sounds, though, like there is some interesting stuff "coming soon" out of the sandbox, so perhaps it's not quite time to move or retire yet? -- Wendy
