I'm not saying more administrators are needed. I'm saying better response time is needed, thats all.
Krzysztof Markus Zywitza pisze: > Any committer can apply patches and every project leader should look > after the issues of his project. More administration is not needed IMHO. > > -Markus > > 2009/4/2 Jonathon Rossi <[email protected] <mailto:[email protected]>> > > I don't want to start a war over why patches aren't applied or > anything. But are there certain projects that patches aren't being > applied for? I know Ayende spent some time a while back to resolve > just about all the logged issues for MK/Windsor. > > I'm really not sure why there was problems around Tim's patch, > there really shouldn't have been, the problem however does seem to > be in our process. > > Maybe we need to assign issues (that have patches) to project > leaders instead of just letting them sit there. If we do assign > issues then project leaders need to be keeping up with these, and > if they can't they really need to reach out to find someone to > help them. > > > 2009/4/2 Krzysztof Koźmic <[email protected] > <mailto:[email protected]>> > > I'm not talking about you applying my patches specifically. > But, there's been many patches submited, not applied for > months. Also Tim Barcz said recently on twitter he got pissed > of, that his trivial patch for nant was not applied and > instead it was disputed over and over. > > I'm not saying there should be one person, but there should be > some SLA-like policy to apply them ASAP. Josh has not have a > commit in 2 years so I'm afraid he's not interested anymore. > > As for regular releases, I wholeheartedly agree, but it's > another, bug topic > > Krzysztof > > Jonathon Rossi pisze: >> 2009/4/2 Krzysztof Koźmic <[email protected] >> <mailto:[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 >> >> > > > > > > > -- > 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 -~----------~----~----~----~------~----~------~--~---
