From: Waylan L. <wa...@gm...> - 2008-12-05 05:09:03
|
On Thu, Dec 4, 2008 at 11:21 PM, Yuri Takhteyev <qar...@gm...> wrote: [snip] > (Again, we can drop 2.3 at some point, if there is a good reason.) [snip] Fyi, Django is currently talking about dropping 2.3 support [1]. It hasn't been decided conclusively yet with some devs on either side of the fence, but they're looking at it. I'll report back on this when I know more. Obviously, we should not do so just because some other package does, but the Django team is very attune to the community at large and a nice way for a small project like ours to gauge these sorts of things. There's some interesting points both for and against in that discussion. I have to wonder if the jump to 2.0 is enough for us to warrant dropping 2.3 support given other, larger projects are looking at doing the same. After all, having a major release (x.0) is a strange place to start issuing depreciation warnings (as some suggest for Django) for 2.3 specific code that will be removed in x.1. That seems silly to me. If we're going to do it, now is as good a time as any. I suppose we'll have to see how things play out for others. [1]: http://groups.google.com/group/django-developers/browse_thread/thread/dcf70c736c204594 -- ---- Waylan Limberg wa...@gm... |