Opened 6 years ago

Closed 4 years ago

#3859 closed task (implemented)

upgrade trac to 0.12

Reported by: erinn Owned by:
Priority: Medium Milestone:
Component: Company Version:
Severity: Keywords:
Cc: karsten Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Debian finally upgraded the version of Trac it has available to 0.12! We should figure out how to upgrade and migrate everything and do it soon. If this is a complex thing, this can be the parent ticket.

http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=trac;dist=unstable

Child Tickets

Change History (6)

comment:1 Changed 6 years ago by karsten

Cc: karsten added

comment:2 Changed 6 years ago by karsten

I talked to weasel, and he says we either need to find somebody to make a backport or install Trac into /srv/trac and take care of it ourselves.

I have no idea how long it can take for a backport to materialize and who we can ask for that. So how about we just install it into /srv/trac?

comment:3 Changed 6 years ago by erinn

I believe the original objection to installing it into /srv/trac ourselves was that weasel wasn't willing to maintain it if it were installed that way. Maybe I'm wrong? I don't think we have anyone who'd be willing to maintain that setup. (By willing I also include people who simply don't have time.)

I'm also not sure how the upgrade path works. That and the admin-time consideration should be examined more.

comment:4 in reply to:  3 Changed 6 years ago by karsten

Replying to erinn:

I believe the original objection to installing it into /srv/trac ourselves was that weasel wasn't willing to maintain it if it were installed that way. Maybe I'm wrong?

My comment above was ambiguous. weasel didn't say he'd maintain a Trac in /srv/trac, but that he'd be fine with having it on a VM he maintains if we found someone maintaining the part in /srv/trac.

I don't think we have anyone who'd be willing to maintain that setup. (By willing I also include people who simply don't have time.)

Could be that nobody would want to maintain it. How much additional effort is it compared to running a backported 0.12? Subscribe to a mailing list and run svn up && make whenever there's an update, plus all the fun when something breaks?

I'm also not sure how the upgrade path works. That and the admin-time consideration should be examined more.

Right. This is independent of whether we compile our own Trac or use a backport, though.

comment:5 Changed 6 years ago by weasel

Owner: weasel deleted
Status: newassigned

comment:6 Changed 4 years ago by karsten

Resolution: implemented
Status: assignedclosed

Our current Trac says it's version 1.0.1, so that makes this ticket obsolete. Closing.

Note: See TracTickets for help on using tickets.