On Jul 27, 2006, at 3:49 PM, [EMAIL PROTECTED] wrote: > Tom Tobin wrote: >> On 7/27/06, Joe <[EMAIL PROTECTED]> wrote: > >> In line with other sentiments I've expressed here in the past: IMHO, >> this means your *project manager* is addled, not Django's release >> process. If you can understand that the development version is >> stable >> enough to use, but your project manager can't, your project manager >> doesn't deserve his title. :p > > First, the django developers are quite egotistical if they are > claiming > that there nightly .95 build is stable, when at any time they could > introduce a bug. The whole point of a release is to do proper testing > and you can say "yes, we froze the code and did tons of testing so we > feel it is stable". > NOT "yeah i hack it everynight and I'm so awsome i never write a > single bug (and my poop doesn't stink -- James Bennett)".
My guess is that no one commits anything without running all the unit tests plus the tests they've written for what they're currently working on. In other words, everything that people were checking worked before should still work now. It may be the case that something that wasn't being checked, but was working anyway, has been broken, but you're not going to figure that out without tests that exercise it. And once you have those, they go back in the tests that people check against before they commit anything. Read about agile development. You can release stable code without freezing it. Todd --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
