Michael Radziej wrote: > Adrian Holovaty schrieb: >> 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? > > Another proposal: > > Let's have a branch of the month, announced on devel and users. The > branch is then frozen, merged with trunk, and will be merged at a fixed > date into trunk if no critical and unfixable bugs are found. This would > encourage at least me to check this branch out and test it well before > the merge ;-)
Branch Tuesday ;) Though I run some commercial projects using an unstable-trunk, policy, I like the stable-trunk approach for Django. It clearly has worked well. In any case, the way to solve branch testing isn't to make the trunk unstable as a convenience. I guess two questions to ask now are a) how many of these branches are realistically going to land, ever, and b) which ones are considered high value, so we can focus on testing those? cheers Bill --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
