#21759: Add persistence for torperf/onionperf -------------------------------+--------------------------------- Reporter: iwakeh | Owner: iwakeh Type: enhancement | Status: merge_ready Priority: Medium | Milestone: CollecTor 1.4.0 Component: Metrics/CollecTor | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -------------------------------+--------------------------------- Changes (by karsten):
* status: needs_review => merge_ready Comment: Hmm, no, that's not what I meant by rebase and squash. The result may be similar, but I find the Git history much easier to use when re-applying commits to master. I also found a flaw in our merge/release order: We said we'd need to release metrics-lib before releasing CollecTor, so that we don't have to depend on a metrics-lib -dev version in a released CollecTor. But we also need to release CollecTor before metrics-lib, or we'd get into trouble with Java 8. Let's not do all this, it's a major PITA waiting to happen. BTDT. I just put `<property name="source-and-target-java-version" value="1.7" />` into metrics-lib's `build.xml`, so that we can put out new metrics-lib versions whenever we need. And I rebased and squashed your earlier task-21759 branch with the goal of merging it as soon as metrics-lib 2.1.0 is out. Now we can still put out new CollecTor versions whenever we need, even if that need arises before metrics-lib 2.1.0 comes out. The result is [https://gitweb.torproject.org/karsten/metrics- db.git/log/?h=task-21759-3 task-21759-3 in my repository]. Changing to merge_ready '''as soon as metrics-lib 2.1.0 is out'''. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21759#comment:22> 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