Closed Bug 714659 Opened 8 years ago Closed 8 years ago
get rid of Standalone Talos
We really should get rid of standalone talos. There are so many differences with it and --develop should account for all the differences that we care about. Talos now has a better installation story and the remaining issues with installation have largely been ticketed and can be dealt with. https://wiki.mozilla.org/StandaloneTalos is also largely outdated and should be eliminated along with this (or at least note as deprecated).
other teams like the networking team use standalone talos. Just need to keep in mind that others depend on this while phasing it out.
With the landing of https://bugzilla.mozilla.org/show_bug.cgi?id=725414 , is there any reason to not get rid of standalone? Are there people on the other teams we should reach out to?
(In reply to Jeff Hammel [:jhammel] from comment #2) > With the landing of https://bugzilla.mozilla.org/show_bug.cgi?id=725414 , is > there any reason to not get rid of standalone? Are there people on the > other teams we should reach out to? Definitely post to dev.platform about this.
So the question is, what is actionable here? The appropriate wiki has already been marked as deprecated
(In reply to Jeff Hammel [:jhammel] from comment #6) > So the question is, what is actionable here? The appropriate wiki has > already been marked as deprecated Are there any repos to remove? How does one actually get standalone talos? Can we put a redirect there that points people to use talos --develop? If we can do that, I think we should do it, and then mark this as fixed.
I've updated all the documentation I can find. Should we close this? Is there anything actionable to do?
+1 for closing
Closing. If there are pages that refer to standalone Talos, we can mark as deprecated and point to https://wiki.mozilla.org/Buildbot/Talos which gives instructions and note the deprecation. AFAIK, there aren't any repos to be closed.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.