Adrian Holovaty wrote: > On 11/7/06, Rob Hudson <[EMAIL PROTECTED]> wrote: >> Adrian Holovaty wrote: >>> That's exactly what we're using the branches for: Things get broken on >>> the branches as branch owner merge in new features. Eventually, bugs >>> get worked out, and they do a code freeze prior to the merge to make >>> the branch as stable as possible. >> I suppose the disadvantage to this is getting users to test branches. > > That's a good point. Maybe we could do a better job of this by > highlighting the currently developed branches on the main Django > download page, rather than hiding them on the wiki, which I'm still > convinced many people don't know about. Thoughts?
(+1000 on the keep-the-trunk-stable approach) i think it's a good idea, but then we also have to make sure that the documentation of the branch is up-to-date, so that it's clear if it's is testing-ready or not, and what it does offer. gabor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
