#29276: Make a release of BridgeDB ----------------------------------+-------------------------- Reporter: ahf | Owner: phw Type: task | Status: assigned Priority: Medium | Milestone: Component: Obfuscation/BridgeDB | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: 5 Reviewer: | Sponsor: ----------------------------------+--------------------------
Comment (by arma): In an ideal world, the goal here would be to make it so a service admin (i.e. not a bridgedb dev) can take the instructions and the build artifact (tarball, git, etc), and arrive at a correctly deployed bridgedb service. Then somebody can install bridgedb somewhere, maintain it, report bugs back to the developers, upgrade when a new release is ready, etc. It is maybe overkill at this point because we don't have a separate service admin who can pick it up and do that -- so putting more structure around the release process might be a waste of our precious time for now. But going through the process once is probably a good idea even if we decide not to put that much formalism around it medium term -- I bet we will find a bunch of surprise changes in the deployed bridgedb service, that you would be unlikely to guess about given what's in git. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29276#comment:7> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs