Couple of ways to do this:
- Have each lib have an assigned maintainer who keeps track of Travis and Cargo health. This already happens for rust-url &c - Set Travis up to reject PRs that do not bump version numbers, and have it run cargo publish on new commits to master (there are enough env vars available to check for branches and PRs). This would be fiddly, but it should work. It would be nice to set up a shell script on servo-s3 and curl it from all travis files (making this process easy to update) -Manish Goregaokar On Fri, May 22, 2015 at 7:19 PM, Josh Matthews <[email protected]> wrote: > https://github.com/servo/rust-harfbuzz/issues/39 is not the first request > to publish certain dependencies on crates.io. I'm in favour of this; the > question is whether we can build in systems that avoid the > publish-and-forget workflow. Thoughts? Should we just go ahead and publish > the latest revision whenever someone asks us to? > _______________________________________________ > dev-servo mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-servo > _______________________________________________ dev-servo mailing list [email protected] https://lists.mozilla.org/listinfo/dev-servo

