#14265: Tag the 1.2.3 release in the repository
------------------------------------+---------------------------------------
Reporter: creecode | Owner: nobody
Status: closed | Milestone:
Component: Uncategorized | Version:
Resolution: fixed | Keywords: tag release
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by shacker):
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.
--
Ticket URL: <http://code.djangoproject.com/ticket/14265#comment:2>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
