2009/4/2 Krzysztof Koźmic <[email protected]> > While we're on it, I think what Castle would benefit from, is an active > community patch manager. > There's a perception, that Castle is veeery slow at incorporating community > patches. > I think there should be a person who whould commit to applying patches with > 24h or starting a discussion on them (if patch is bigger, or controversial) > and apply them/dismiss within reasonable time. >
OT: Sorry I have been really slow applying your DP patch. I do however see having a single patch manager a very big task to assign to someone. Josh is/was the patch manager, but I think this task has been split up to get project leads to apply the patches because there was too much of a burden on one person and to make sure it aligns properly with the project. I think to break most of the bad perceptions people have about Castle would be to have regular releases that include the patches that people submit. The releases don't have to include massive loads of fixes or new functionality, just enough for it to be worthwhile for people to upgrade. -- Jono --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
