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 probably be around in one form or another.



On Tue, Jul 29, 2014 at 4:11 PM, Alex Crichton <a...@crichton.co> wrote:

> Currently the threshold for being "officially supported" will be one
> of being in the rust-lang organization or being on the travis
> dashboard. At this time there are no plans to have an in-tree way to
> distinguish, although I suspect that a README with a description would
> likely suffice.
>
> On Tue, Jul 29, 2014 at 3:45 PM, 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 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]: https://github.com/rust-lang/hexfloat/blob/master/.travis.yml
> >> [2]: http://buildbot.rust-lang.org/travis/travis.html
> >
> >
> > So going forward...
> >
> > Where can we look in source / folders / files ... to see what is an
> > "officially supported repository" and what is not ?  Let's say I don't
> want
> > to have to look at the Travis view for that info, but just look at
> source to
> > figure this out.
> >
> > --
> > -Thad
> > +ThadGuidry
> > Thad on LinkedIn
> _______________________________________________
> Rust-dev mailing list
> Rust-dev@mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
>
_______________________________________________
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev

Reply via email to