There was a bit of discussion on the PR I submitted yesterday:
https://github.com/servo/webrender/pull/1644#discussion_r136424367 -
we decided to just manually bump it once in a while instead of making
it track `stable`.
On Thu, Aug 31, 2017 at 5:54 PM, Mike Hommey wrote:
> On Thu, Aug 31, 2017 a
On Thu, Aug 31, 2017 at 10:27:55AM -0500, Jack Moffitt wrote:
> Specifically for webrender (and anything else under the servo org on
> GitHub), you can just file a bug and assign to edunham and we'll fix
> that up.
>
> jack.
Note that for webrender specifically, it used to build against stable,
b
Specifically for webrender (and anything else under the servo org on
GitHub), you can just file a bug and assign to edunham and we'll fix
that up.
jack.
On Thu, Aug 31, 2017 at 10:25 AM, Kartikaya Gupta wrote:
> Do we have a policy on CI coverage for vendored rust libraries? I'm
> concerned for
Do we have a policy on CI coverage for vendored rust libraries? I'm
concerned for example that we depend on a number of third-party rust
libraries that don't do CI builds against rust stable and so it's
possible they might break. I discovered that webrender CI for example
is currently only building
This is great - thanks Ralph!
On Tue, Aug 1, 2017 at 11:53 AM, Ralph Giles wrote:
> We've formalized a new plan for when we update the minimum-required Rust
> version for building Firefox. Starting later this week we'll require the
> latest stable Rust two weeks after it is released.
>
> This me
5 matches
Mail list logo
