Opened 14 years ago
Closed 14 years ago
#14267 closed (fixed)
Trac Upgrade Tracking Ticket
Reported by: | Armin Ronacher | Owned by: | Armin Ronacher |
---|---|---|---|
Component: | *.djangoproject.com | Version: | 1.2 |
Severity: | Keywords: | ||
Cc: | justinlilly@… | Triage Stage: | Accepted |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The upcoming upgrade to Trac 0.12 requires the following yet outstanding changes:
- the antispam plugin has to be evaluated and tested with 0.12
- is the XMLRPC plugin in use?
- install batch notify
Change History (7)
comment:1 by , 14 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 14 years ago
I want a pony: if there was a way to download a patch file directly from the ticket page, rather than having to click on the patch link and then scroll to the bottom to hit another link to download as original. So, still keep the Trac colored diff view, but add another link on the right of the patch list to "download as original" or "download as raw text".
Thanks. :-)
comment:3 by , 14 years ago
The new trac has a small button next to the filename with a download symbol. Click that and you get your raw patch :)
comment:4 by , 14 years ago
It might be worth considering going straight to a 0.12.x checkout of Trac. The 0.12.1 stabilization release seems to be near (5 of 53 tickets left open): http://trac.edgewall.org/milestone/0.12.1
comment:5 by , 14 years ago
Status: | new → assigned |
---|
I don't see the value. Trac upgrades are painless. The reason the one we are doing currently is not is that they changed the template engine which broke this design and some other things like plugins. Going from 0.11 to 0.12.1 with or without intermediate versions is a process of a couple of seconds.
comment:6 by , 14 years ago
Cc: | added |
---|
comment:7 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Closing since we are now on 0.12.2
We talked about that during the DjangoCon sprint extensively and performed the upgrade locally. New configuration files are available, please ask mitsuhiko or jezdez about it.