On 9/10/07, Christopher Lenz <[EMAIL PROTECTED]> wrote: > 1) Too many changes with too much impact > trac.context and the flexible permissions system, that have gone in > without ever having been completed on a branch, or without having
I feel I have to defend my decision to merge only the Wiki part of the permission system. Given the same situation I would make the same decision again, so I'm not apologising, I'm justifying :) The primary reason was that keeping a branch updated against Trac trunk, particularly one that due to its very nature touches a large part of the code base, is a draining experience. This is mainly due to the high rate of change on trunk. The second reason was that even though I waited two weeks for review, I would have liked more input. With that in mind, if anybody had raised major concerns after the merge, reverting just the Wiki changes would have been relatively easy. With my excuses^Wreasoning out of the way, I think the recently proposed changes to how we develop Trac (development occuring exclusively in branches, a decent review process, etc.), would have helped massively with both of these problems. C'est la vie. > 2) Too many API changes without much benefit > 3) Added bloat > 4) Not enough testing All agreed. > 5) Not enough communication > The trac-dev mailing list has been extremely quiet. A lot of > discussion is taking place exclusively on IRC and on tickets, and > that means that anyone who doesn't have the bandwidth to follow those > channels (which are both very high traffic, and often with a bad > signal-to-noise ratio) is out of the loop. Let's *please* get > development discussions on this list. This is a very good point, and one echoed by several others already in this thread. I agree wholeheartedly. > So that was me venting. I hope I didn't upset anyone too much, and > that I made my point of view reasonably clear. I think the venting was quite coherent :) > I also think we really need to get away from these feature-packed > releases, and move towards releasing often and early. And we need to > stop adding features over features to the core, and instead > concentrate on getting the infrastructure in place to be able to > release a 1.0 version sometime this millenium. I can't agree more. I think the wider Internet has shown that releasing often and early helps keep projects vibrant and healthy. And I think the rot that's setting in to Trac illustrates what happens when this doesn't happen. -- Evolution: Taking care of those too stupid to take care of themselves. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
