2 ms·
"Putting out buggy code on time simply isn't an option" This is why opensource is so nice. If you want buggy code, you download the trunk, its not forced on yo
by jhawk28 17y ago
"Putting out buggy code on time simply isn't an option"
This is why opensource is so nice. If you want buggy code, you download the trunk, its not forced on you.
- slig 17y agoAFAIK, the Django trunk is stable.
- jacobian 17y agoThat's right: our policy (http://docs.djangoproject.com/en/dev/internals/contributing/#branch-policy http://docs.djangoproject.com/en/dev/internals/contributing/...) is that, whenever possible, trunk be kept stable. "People should be able to run production sites against the trunk at any time." This isn't hyperbole: I have sites in production that run against trunk and are updated very frequently. That said, like all software, Django has bugs. There's a handful (45 right now) left (http://code.djangoproject.com/query?status=!closed&component=!Translations&component=!Documentation&milestone=1.1 http://code.djangoproject.com/query?status=!closed&compo...) that are serious enough to prevent calling anything "final" right now.
- tdavis 17y agoI always run trunk as well, seeing as how it always has more kickass stuff than the release. The only bug I've ever had to directly work around is the "EmptyQuerySet sucks" bug (http://code.djangoproject.com/ticket/7235 http://code.djangoproject.com/ticket/7235).