[ANN] Django 1.2.3 released

[James Bennett]

To correct several issues in the 1.2.2 package earlier this week,
tonight the Django team has issued Django 1.2.3. Details are available
on the Django weblog:

http://www.djangoproject.com/weblog/2010/sep/10/123/

All users are encouraged to upgrade as soon as possible.

--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."

[shacker]

On Sep 11, 12:00 am, James Bennett <ubernost...@gmail.com> wrote:
> To correct several issues in the 1.2.2 package earlier this week,
> tonight the Django team has issued Django 1.2.3. Details are available
> on the Django weblog:
>

It looks like there is no svn tag for 1.2.3:

http://code.djangoproject.com/svn/django/tags/releases/

which affects those of us who use pip requirements files for version
maintenance.

Thanks,
Scot

[creecode]

I too find the tagged releases useful. Thanks for all your hard work
people!

Toodle-looooooooooooo.............
creecode

[creecode]

Hello all,

I asked < http://code.djangoproject.com/ticket/14265#preview > and we
received! :-) Thanks Russell!

[shacker]

On Sep 12, 12:12 pm, creecode <creec...@gmail.com> wrote:
> Hello all,
>
> I asked <http://code.djangoproject.com/ticket/14265#preview> and we
> received! :-)  Thanks Russell!

Hmm, the ticket is marked fixed, but the repo is still at 1.2.1. This
is not good. 1.2.2 is a security release, and we should be able to use
the official distribution mechanism (svn) to update our sites
immediately.

./s

[shacker]

On Sep 13, 8:19 am, shacker <shac...@birdhouse.org> wrote:

> Hmm, the ticket is marked fixed, but the repo is still at 1.2.1. This
> is not good. 1.2.2 is a security release, and we should be able to use
> the official distribution mechanism (svn) to update our sites
> immediately.

OK, 1.2.3 is there now.

http://code.djangoproject.com/svn/django/tags/releases/

Thanks,
Scot

[Tom Evans]

svn is the 'official' vcs, and is used to manage the development (and
one would hope) the release engineering, but I doubt very much that it
is the 'official distribution mechanism'; I would have thought that
would be the tarball. Indeed, the release notes make no reference to
svn.

It is useful to have the tags in svn, but given that it is not in any
way the release mechanism, it's a little unwise to rely upon it. YMMV.

Cheers

Tom

[James Bennett]

On Thu, Sep 23, 2010 at 5:42 AM, Tom Evans <teva...@googlemail.com> wrote:
> svn is the 'official' vcs, and is used to manage the development (and
> one would hope) the release engineering, but I doubt very much that it
> is the 'official distribution mechanism'; I would have thought that
> would be the tarball. Indeed, the release notes make no reference to
> svn.

Correct. The one and only official release mechanism is via the
packages listed on the Django downloads page.

We do tag things in SVN as a convenience (and for historical
purposes), and keep code organized into release-specific branches
people can deploy from if they want to, but the answer to the question
"what is Django 1.2.3" is "the file Django-1.2.3.tar.gz listed on the
downloads page".