> On 11/7/06, Rob Hudson <[EMAIL PROTECTED]> wrote: >> I think this is a self-imposed limitation to allowing a branch that's >> close to be merged to trunk to get more testers. For myself, I'd much >> rather see some broken things on trunk on occasion if that means it is >> easier to develop and move Django forward. >> ...
Adrian Holovaty: > The self-imposed limitation to making trunk usable at all times is one > of the things I particularly like about our arrangement. It's mostly > for developer convenience, so fans of the latest-and-greatest can > simply "svn update" their Django codebase to get the latest, with > minimal breakage. It's all the convenience of daily builds with none > of the upgrade overhead. I like this, too. Perhaps having an additional testing branch with the more mature branches merged with each other and the latest branch would satisfy the various requests for merged branches. This would require a kind of release team which deals with the merge conflicts, running tests, keeping contact to branch maintainers. No stability guaranteed whatsoever. Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
