There's a cron job running which will trigger each build each night
after the nightlies have finished building, and the .travis.yml script
for these repos are all wired to nightlies rather than the PPA.
Could the source code for this cron job be published, with instructions on
how to get
On 29/07/14 23:30, Alex Crichton wrote:
[...]
We plan to implement any necessary infrastructure to ensure that the crates
move out of the rust repository maintain the same level of quality they
currently have.
Will these crates’ documentation be available online?
In rust-url, rust-cssparser,
Ok, I got the basic going with a temporary for of `libsemver` here:
- https://travis-ci.org/errordeveloper/rust-libsemver/builds/31217706
- https://github.com/errordeveloper/rust-libsemver
Few questions:
- should I bother with enabling OS X beta on Travis?
- what naming convetion we
We plan to implement any necessary infrastructure to ensure that the
crates
move out of the rust repository maintain the same level of quality they
currently have.
Will these crates’ documentation be available online?
At this time there are no plans for this, but we're certainly open to
Ok, I got the basic going with a temporary for of `libsemver` here:
- https://travis-ci.org/errordeveloper/rust-libsemver/builds/31217706
- https://github.com/errordeveloper/rust-libsemver
Awesome! I've created a new repo for you to make a PR against:
https://github.com/rust-lang/semver
I'd like to suggest - assuming it's not implied - that all aforementioned
PRs should preserve history to date, rather than just having a copy of the
files as they are at present.
Decent walkthrough using a subtree merge -
On 30/07/14 15:59, Alex Crichton wrote:
We plan to implement any necessary infrastructure to ensure that the
crates
move out of the rust repository maintain the same level of quality they
currently have.
Will these crates’ documentation be available online?
At this time there are no plans
[snip]
2. A status page [2] is provided to get a quick glance at the status of all
officially supported repositories.
The amount of infrastructure around keeping these repositories up to date
will likely change over time, but this is the current starting point for
automation.
[1]:
They are still officially supported, but they will live in
https://github.com/rust-lang/ instead of with the Rust compiler.
On 30 July 2014 06:45, Thad Guidry thadgui...@gmail.com wrote:
[snip]
2. A status page [2] is provided to get a quick glance at the status of
all
officially
One additional way for us to say inside rust itself if a library is
officially supported would be for us to the #[experimental] / #[unstable] /
#[stable] / etc tags inside the https://github.com/rust-lang/ libraries.
#[experimental] libraries may or may not survive, but #[unstable] and above
will
10 matches
Mail list logo
