[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #3859 [Company]: upgrade trac to 0.12
#3859: upgrade trac to 0.12
---------------------+------------------------------------------------------
Reporter: erinn | Owner: weasel
Type: task | Status: new
Priority: normal | Milestone:
Component: Company | Version:
Keywords: | Parent:
Points: | Actualpoints:
---------------------+------------------------------------------------------
Comment(by karsten):
Replying to [comment:3 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.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3859#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs