Tag the 1.2.3 release in the repository

[creecode]

It would help some of the users if release 1.2.3 could be tagged < ​http://groups.google.com/group/django-users/browse_thread/thread/97ec4d71d1a2a503# > in the repository.

[Russell Keith-Magee]

Fixed in [13762] and [13763].

[Scot Hacker]

This ticket is marked fixed, but the svn repo still shows 1.2.1 as the latest tagged branch. This is a security release, and it's critical that the official distribution tool (svn) be kept up to date so sites can update immediately through their pip requirements files.

After all the talk at Djangocon about svn vs. other DVCSs, and the news that few of the core devs were obtaining Django through svn at all, and this lateness in updating the svn tag, the message being sent is that no one in a position of control is watching the official distribution mechanism very closely, even when security is concerned.

[Karen Tracey]

I don't know what you mean when you say "svn repo still shows 1.2.1 as the latest tagged branch". Here:

​http://code.djangoproject.com/browser/django/tags/releases

shows 1.2.2 and 1.2.3. It was done late, and I'm not sure why (packaging is not my thing) but I'm not sure now what it is exactly that is still missing?

[Scot Hacker]

I use this URL: ​http://code.djangoproject.com/svn/django/tags/releases/

You're right - 1.2.3 is there now, but it wasn't an hour ago (I had even done a cache-bypassing super refresh in my browser to make sure).

Thanks to whoever pushed it through.