Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#14265 closed (fixed)

Tag the 1.2.3 release in the repository

Reported by: creecode Owned by: nobody
Component: Uncategorized Version:
Severity: Keywords: tag release
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


It would help some of the users if release 1.2.3 could be tagged < > in the repository.

Change History (4)

comment:1 Changed 6 years ago by Russell Keith-Magee

Needs documentation: unset
Needs tests: unset
Patch needs improvement: unset
Resolution: fixed
Status: newclosed

Fixed in [13762] and [13763].

comment:2 Changed 6 years ago 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.

comment:3 Changed 6 years ago by 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:

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?

comment:4 Changed 6 years ago by shacker

I use this URL:

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.

Note: See TracTickets for help on using tickets.
Back to Top