I fully agree with this: a 0.92 made of trunk, with all fixes collected on trunk. Perhaps patches applied for concurrency/threading issues and memory leaks -- that would be great for stability, esp. on windows. Then instantly switch trunk to m-r, and if m-r is good enough, make a release of it.
Cheers, --Tim -----Original Message----- From: django-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of David S. Sent: vrijdag 14 april 2006 17:23 To: django-users@googlegroups.com Subject: Re: Fate of 0.91 projects Jeroen Ruigrok van der Werven <ashemedai <at> gmail.com> writes: > On 4/14/06, Kenneth Gonsalves <lawgon <at> thenilgiris.com> wrote: > > next release *must* be magic removal - no point doing any interim ... > Better to bite the bullet and get this over with. ... I was thinking simultaneous release. Really just for the sake of a label for the pre-magic removal stuff. This is not about "biting the bullet" or any of that. I am talking about projects that are complete and for which it would be mighty convenient to have the last and best code to run on. When it comes time for rev 2, we'll be happy to move to 1.x or whatever Django is at. Of course, it can always be fetched from SVN, it just feels better to have a nice EGG for your disaster recovery stack. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users -~----------~----~----~----~------~----~------~--~---
