That makes sense, thanks for the explanation and the pointers to the
best sources of information.  I never realized the Django announce
mailing list existed, it will serve my purposes perfectly as I'm sure
it's intended to!

Regards,
Josh

On Apr 2, 9:02 pm, Russell Keith-Magee <[email protected]>
wrote:
> Hi Josh,
>
> In short, no - Twitter isn't a particularly reliable source for updates.
> Someone in the core team will usually tweet about the release, but since
> it's hard to share logins to a single Twitter account, and the person who
> owns Django's twitter account won't always be involved in formally cutting
> the release, we sometimes drop the ball.
>
> Our official channels are the django-announce mailing list, and Django's
> blog. If you're looking for guaranteed notification, those two channels are
> guaranteed to receive notification.
>
> Yours
> Russ Magee %-)
>
>
>
>
>
>
>
> On Wed, Apr 3, 2013 at 12:10 AM, Josh Cartmell <[email protected]> wrote:
> > Thanks for the release!
>
> > Kind of random question, but this seems like the best place to ask
> > it.  I used to use Twitter mobile notifications to keep up with Django
> > releases, but I've noticed that the last three releases (since 1.4.4)
> > have not been announced on Django's Twitter.  Is this just an over-
> > site, or is Twitter no longer a good place to keep up with Django
> > releases.
>
> > Thanks,
> > Josh
>
> > On Mar 28, 2:02 pm, Jacob Kaplan-Moss <[email protected]> wrote:
> > > Hi folks --
>
> > > We've just released Django 1.5.1, a bug fix release that cleans up a
> > > couple issues with last month's 1.5 release.
>
> > > The biggest fix is for a memory leak introduced in Django 1.5. Under
> > > certain circumstances, repeated iteration over querysets could leak
> > > memory - sometimes quite a bit of it.
>
> > > For more details, see our announcement:
>
> > >    https://www.djangoproject.com/weblog/2013/mar/28/django-151/
>
> > > Thanks for using Django!
>
> > > Jacob
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Django developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to [email protected].
> > To post to this group, send email to [email protected].
> > Visit this group athttp://groups.google.com/group/django-developers?hl=en
> > .
> > For more options, visithttps://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to