Travis: consider running CI on beta, nightly, and tor's lowest supported rust

At the moment, Tor's Travis CI runs on stable rust, and our Appveyor (Windows) CI doesn't run rust at all (#26954 (moved)).

But in our privcount_shamir work (#25669 (moved)), we've discovered some important bugs by running beta and nightly.

Since Rust releases every 6 weeks, we should run CI on rust stable and beta, so that we catch any show-stoppers before they are stable.

We might also want to consider an allow_failures nightly build.

If we choose to support a lower version of rust than stable (when a major distro freezes on a lower version), we should also CI that version.

changed milestone to %Tor: unspecified

added 040-unreached-20190109 041-accepted-20190115 041-deferred-20190530 component::core tor/tor milestone::Tor: unspecified points::1 priority::medium privcount rust severity::normal status::new teor-unreached-2019-03-08 tor-ci type::enhancement labels

Fix title

Trac:
Summary: Travis: consider running CI on stable and beta rust to Travis: consider running CI on beta, nightly, and tor's lowest supported rust

Trac:
Cc: N/A to dmr

Correct privcount shamir ticket.

Trac:
Description: At the moment, Tor's Travis CI runs on stable rust, and our Appveyor (Windows) CI doesn't run rust at all (#26954 (moved)).

But in our privcount_shamir work (#24629 (moved)), we've discovered some important bugs by running beta and nightly.

Since Rust releases every 6 weeks, we should run CI on rust stable and beta, so that we catch any show-stoppers before they are stable.

We might also want to consider an allow_failures nightly build.

If we choose to support a lower version of rust than stable (when a major distro freezes on a lower version), we should also CI that version.

to

At the moment, Tor's Travis CI runs on stable rust, and our Appveyor (Windows) CI doesn't run rust at all (#26954 (moved)).

But in our privcount_shamir work (#25669 (moved)), we've discovered some important bugs by running beta and nightly.

Since Rust releases every 6 weeks, we should run CI on rust stable and beta, so that we catch any show-stoppers before they are stable.

We might also want to consider an allow_failures nightly build.

If we choose to support a lower version of rust than stable (when a major distro freezes on a lower version), we should also CI that version.

Tor 0.3.6.x has been renamed to 0.4.0.x.

Trac:
Milestone: Tor: 0.3.6.x-final to Tor: 0.4.0.x-final

These tasks are on the 0.4.1 roadmap for PrivCount and Sponsor V.

Trac:
Milestone: Tor: 0.4.0.x-final to Tor: unspecified
Keywords: N/A deleted, 041-proposed, 040-unreached-20190109 added

Let's review these tickets at the next meeting using our 041-proposed process.

They're on the roadmap, so the review should focus on ticket size and team capacity (and sponsor expectations).

Trac:
Milestone: Tor: unspecified to Tor: 0.4.1.x-final
Keywords: 041-proposed deleted, 041-proposed-on-roadmap added

Trac:
Points: N/A to 0.5

We accepted this in the meeting.

Trac:
Keywords: 041-proposed-on-roadmap deleted, 041-accepted-20190115 added

This is sponsor V or sponsor 31.

Trac:
Sponsor: N/A to SponsorV

Trac:
Points: 0.5 to 1

Trac:
Sponsor: SponsorV to SponsorV-can

Unassign myself from -can tickets.

Trac:
Owner: teor to N/A
Keywords: N/A deleted, teor-unreached-2019-03-08 added

Marking these tickets as deferred from 041.

Trac:
Keywords: N/A deleted, 041-deferred-20190530 added

Trac:
Milestone: Tor: 0.4.1.x-final to Tor: unspecified

Removing sponsor V as we do not have more time to include this tickets in the sponsor.

Removing sponsor from tickets that we do not have time to fit in the remain of this sponsorship.

Trac:
Sponsor: SponsorV-can to N/A

Change tickets that are assigned to nobody to "new".

Trac:
Status: assigned to new

changed time estimate to 8h