Re: [dev-servo] The future of irc.mozilla.org/#servo

Has anybody got experience with the Discord<->Matrix bridge ( https://matrix.org/bridges/#discord )? Like the rest of Mozilla, I don't particularly enjoy Discord's terms of service / privacy policy, but I'm part of a zillion Discord servers for other communities. Whereas #servo IRC is my last rema

Re: [dev-servo] ./mach build vs. cargo build

Cargo has traditionally not wanted to add full support for arbitrary RUSTFLAGS, for reasonable reasons: https://github.com/rust-lang/cargo/issues/60#issuecomment-51705597 What we've done in the past is for each flag that we needed exposed opened a specific Issue or PR to Cargo to have just that on

Re: [dev-servo] Standalone NDK concerns?

The standalone NDK's problem is that we moved to use the same C++ standard library as Firefox in order to match SM when Gecko made the move. Unfortunately, the make-standalone-toolchain.sh script was broken for years for anything apart from the default C++ standard library (it would either just bre

Re: [dev-servo] Dropping CEF support?

I've talked with the CEF owner, Mike from Samsung, and given how long the blocking issues (see below) have been open and preventing use of or additional work on CEF, he's OK with removing the support. - Lars https://github.com/servo/servo/issues/10274

Re: [dev-servo] Dropping CEF support?

What does "3rd party project" mean in this case? It's not clear to me how you could do a CEF wrapper externally without forking and removing glutin entirely. At a higher level, I guess I'm concerned that CEF is the only vehicle we currently have for testing Servo within a full-featured browser she

Re: [dev-servo] PSA: Avoid invoking Debug formatters in release-mode Rust

At least for Servo, should we add a check to tidy ( https://github.com/servo/servo/blob/master/python/tidy/servo_tidy/tidy.py) immediately to catch the use of that fairly-unique formatting string, as we do for a bunch of other random stuff? We can always exempt particular files/folder where we thin

Re: [dev-servo] [stylo-team] Mozilla central backout support arriving to Servo later this week

Opinions vary. From my point of view, if we attempt another subsystem transplant across a code boundary that lacks clean separation (e.g., parallel layout), then we will continue to need this coupling in the future. If we instead get to a point where most of the modules that Firefox is using from

[dev-servo] Mozilla central backout support arriving to Servo later this week

tldr: If you see some PRs from the moz-servo-sync GitHub user with a priority of "treeclosed," it's because those must be landed into Servo ASAP to support Firefox backouts. Due to some amazing work from gps, we already have support for taking code changes that occur in Servo on Github and automat

Re: [dev-servo] Improved OSX BuildBot Capacity

Thanks so much for driving this! We've now gone from over 1.5 hours per build to about 53 minutes, with prospects of getting even lower once Rayon is updated and we get sccache for Rust in place. Great work! - Lars On Wed, May 31, 2017 at 12:45 PM, Emily Dunham wrote: > Good morning, superb Ser

[dev-servo] Proposal: remove testing of and support for MinGW builds

Servo used the excellent MinGW toolchain to quickly stand up Servo builds on Windows and to provide us with Windows debugging support while the MSVC Rust toolchain was not yet ready. Now that the native MSVC is working well, we would like to remove testing of and support for those MinGW builds. Mi

Re: [dev-servo] Android support

Thanks for driving this, Fabrice! That sounds like a great outline. From the VR side, indeed what we're basically looking for is full screen app support and WAY better integration with the Android lifecycle model (orientation changes, background/foreground/close, intent handling, etc.). I apologize

[dev-servo] Gating on Android and Windows MSVC

Just wanted to make a public service announcement that: 1) We are gating on Android again. The fine team at Szeged working on Web Bluetooth also helped pick our Android builds back off the floor after the libc++ changes and we've re-enabled Android. Thanks to mmatyas and dati for all their hard wo

[dev-servo] Mozilla's Project Quantum and Servo

This morning Mozilla announced Project Quantum (http://bit.ly/2dLTOv7 ), a coordinated effort to dramatically improve the user experience of the web engine inside of Firefox. A key part of Quantum (https://wiki.mozilla.org/Quantum ) is the work to include two Servo subsystems in Gecko: # Servo’s s

Re: [dev-servo] Weekly status updates

On Mon, Sep 26, 2016 at 12:36 PM, Olaf Buddenhagen wrote: > As a spare time outside contributor, it has become pretty much > impossible for me to stay informed of what's happening in Servo land, > since the meetings (and thus the meeting notes) have been cancelled; > while few things are going ove

[dev-servo] Weekly status updates

I've noticed that while some people are still submitting their weekly status updates on http://statusupdates.dev.mozaws.net/ (thank you!), it's both not everybody and we're missing a bunch of the more active community members who might like to highlight their work. I'd love to either get that movi

[dev-servo] Welcoming Josh Matthews to the Servo core team

We are delighted to announce that Josh Matthews is joining the Servo core team (https://github.com/servo/servo/wiki/Governance). Josh (jdm on IRC and GitHub) has driven planning for the DOM for several years, coordinates most of our community programs, and is already a contributor to other major d

Re: [dev-servo] Proposal: remove mingw Servo builds in favor of msvc

should kill it off any time soon, but we should switch > the default to MSVC and limit the amount of msys2 dependencies we have.. but > we should still be able to build. > > - Vlad > > On Thursday, September 8, 2016 at 11:08:17 AM UTC-4, Lars Bergstrom wrote: >> Now th

Re: [dev-servo] Proposal: remove mingw Servo builds in favor of msvc

On Thu, Sep 8, 2016 at 11:01 AM, Gregory Szorc wrote: > > I would favor going the Clang route for supporting building with OSS on > Windows. MinGW for better or worse is not just a toolchain: it's a mini > UNIX install on your machine. From my experience, all that extra surface > area just introdu

[dev-servo] Proposal: remove mingw Servo builds in favor of msvc

Now that Vlad has landed the amazing support for compiling with Visual C++ instead of the mingw gcc toolchain, I'd like to propose that we remove mingw from our automation, documentation, and support. There are a few reasons: 1) Python is a total crazy mess. Users get messed up with the three (3) d

Re: [dev-servo] Servo testing as part of PhD dissertation

On Wed, Sep 7, 2016 at 10:55 AM, Geoffrey Sneddon wrote: >> >> However I think you might make progress with some sort of >> consensus-based approach e.g. take a testcase and render it in >> gecko/blink/webkit/edge. If the difference by some metric (e.g. number >> of differing pixels, although more

Re: [dev-servo] Moving style out of tree as an alternative to frankenbuild?

On Thu, Aug 25, 2016 at 1:55 PM, Manish Goregaokar wrote: > > There are a lot of issues with this. I agree that there are challenges with mirroring the root Servo repository into m-c, but I'd like to make sure we mention some of the positives that we get from it: - Having "servo" in-tree means th

[dev-servo] The size of the tests/ directory

Currently, the GitHub Servo repository has 134,062 files... 131,477 of which are in the tests/ directory. Of those, 102,871 are in the CSS WG tests. I know it's not a perfect measure, but that's also 862megs of the 1.132gb of disk space usage reported by `du` on macOS for a Servo checkout. So, I'd

Re: [dev-servo] Mentors needed (on IRC)

This is very exciting! Shing, since you will be there in-person, if you could capture some of the difficulties that people encounter when first getting started - even if they overcome it themselves - I'd really appreciate it! I don't have a good sense for how many people give up on contributing to

Re: [dev-servo] Proposed work for upcoming sharing of Servo components with Firefox

On Mon, Aug 8, 2016 at 11:16 AM, Olaf Buddenhagen wrote: > >> This seems to trade time for machines by optimistically assuming all >> previous PRs passed tests. > > Right. > > As long as intermittent failures are rare, I think it's a fair > assumption. (Actual bugs showing up in pre-commit testing

Re: [dev-servo] Web console protocol support for Servo

> On Jul 8, 2016, at 10:36 PM, Manish Goregaokar wrote: > >> Our understanding is that your plan was to take out your Firefox devtools >> protocol support and start implementing the Chrome protocol, once your June >> demos were done. Have you started work on this? > > Not that I am aware of. I'd

Re: [dev-servo] Proposed work for upcoming sharing of Servo components with Firefox

On Jun 21, 2016, at 8:39 AM, Boris Zbarsky wrote: > On 6/21/16 8:34 AM, Lars Bergstrom wrote: >> If a backout lands as a `git revert` of the offending commit(s) I'm >> certainly less concerned, as that's annoying but not impossible for people >> to continue rebas

Re: [dev-servo] Proposed work for upcoming sharing of Servo components with Firefox

On Jun 20, 2016, at 9:25 PM, Boris Zbarsky wrote: > > On 6/20/16 8:35 PM, Lars Bergstrom wrote: >> Backouts came up in the discussion, and I tried to make it pretty clear that >> they are not compatible with a GitHub-style development model (even if you >> *could*

Re: [dev-servo] Proposed work for upcoming sharing of Servo components with Firefox

On Jun 20, 2016, at 5:18 PM, Jack Moffitt wrote: > > I think the idea was that Servo code won't land until post-commit > Gecko tests pass? Otherwise I'm not sure what we do about Gecko side > backouts. The last thing I was told is that we would be landing Servo commits to a branch that is *neve

Re: [dev-servo] Proposed work for upcoming sharing of Servo components with Firefox

> On Jun 20, 2016, at 10:16 AM, Jack Moffitt wrote: > >> 2) Move webrender and webrender_traits back into the Servo repository. > > WebRender has a small and stable API. This API didn't even need to > change in WebRender 2 from my understanding. This means we'll be > moving a very low coupling d

[dev-servo] Proposed work for upcoming sharing of Servo components with Firefox

As many of you may have seen from the document (https://docs.google.com/document/d/1uubYE7JXaVY10PoAY9BVx8A-T11ZxP1RYqNOrFJwdcU/edit) and discussions on dev-build and at the workweek, we have an increasing desire to be able to try to develop and potentially ship Servo code in Firefox. While this is

[dev-servo] Editing the wiki now requires collaborator access

After removing a random thing added to our official Planning Roadmap yet again, I've decided to make our wiki (https://github.com/mozilla/servo/wiki/) editable only by collaborators. So, as with labeling issues, anybody who edits these pages needs to be in the Developers group in the Servo GitHub o

Re: [dev-servo] Proposal: cancel the weekly meeting

ng the standing meeting. >> >> jack. >> >> On Sun, Apr 17, 2016 at 11:31 AM, Lars Bergstrom >> wrote: >> > On Thu, Apr 14, 2016 at 2:46 PM, Manish Goregaokar >> > wrote: >> >> >> >> So yeah, +1 for cancelling. I do look forward

Re: [dev-servo] Proposal: cancel the weekly meeting

On Thu, Apr 14, 2016 at 2:46 PM, Manish Goregaokar wrote: > > So yeah, +1 for cancelling. I do look forward to the meetings, since they > give a nice overview of what's going on, > but TWiS should be capable of filling in that gap and the meetings aren't > happening anyway. At this point, we have

[dev-servo] Meeting notes from chat with the Devtools team

We talked about: - Short and long-term plans for devtools protocol implementations - Devtools.html UI - Privileged JS - Supervisory JS - Architecture-related stuff - Some longer-team feature ideas https://github.com/servo/servo/wiki/Meeting-Devtools-Servo-2

[dev-servo] Proposal: cancel the weekly meeting

I'd like to propose that we cancel the weekly meetings and move the discussions to an asynchronous medium (mailing list or GitHub Issues, as appropriate). As the project has matured and the team has grown, the weekly meeting has become less useful. We can't (and shouldn't!) make decisions there be

Re: [dev-servo] Support for B2G OS (community effort) and long term plans

Hi, Enrico! Right now, I think that the best strategy for the B2G OS effort is to continue to be powered by Gecko and to pick up Servo components as we upstream them there through the Oxidation effort. In the short term, Servo's priorities, especially around device support, rely on APIs such as O

Re: [dev-servo] Please don't leave PRs without an assignee

I think that it would be nice if our highfive had the feature that Rust's does (IIRC) where it can assign a reviewer based on area of interest. If you're referring to the governance list on the wiki (https://github.com/servo/servo/wiki/Governance#super-reviewers), it's not outdated, but just a dif

[dev-servo] Weekly meeting 2016-03-07 (Windows CI; reviewable; maintainers; tree layout; browser.html recap; intermittents; promises)

Meeting notes available here: https://github.com/servo/servo/wiki/Meeting-2016-03-07 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

[dev-servo] PSA: incoming Windows CI (AppVeyor)

We are in the process of enabling Windows CI on the main Servo repository. We're using Homu + AppVeyor (http://appveyor.com/) to do the testing, in a similar manner to how we use Homu + Travis on other repositories. Current Linux and Mac builds will still be performed on our BuildBot configuration.

Re: [dev-servo] Fwd: Re: Suggested code review workflow

This may also be less of a big deal here at Mozilla, where there's (presumably?) only been one bug database since 1998 and will only be one forever, but when I was at MS, I had to make accessibility fixes in some code that was a bit more than 20 years old, and "fixes B1#2003" is really tough to tra

[dev-servo] Please comment on your reviewable.io perf issues!

For the people doing lots of reviews in reviewable.io, Please comment in https://github.com/Reviewable/Reviewable/issues/251 (or create new issues) on your performance scenarios when reviewing large diffs. I personally like to load the whole thing, scroll through, and be able to use search within

[dev-servo] Meeting 2016-01-25 (Meeting times; build stats; Windows; homu; projects)

https://github.com/servo/servo/wiki/Meeting-2016-01-25 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

Re: [dev-servo] Using Cargo in Gecko

Thanks for doing this investigation, Valentin! I'm a little bit worried about the mechanics of auto-upstreaming: - How do we handle commit access? Having the upstream maintainers (none of whom might be current Gecko peers) correctly identified and doing reviews in bugzilla to ensure m-c pushes can

[dev-servo] Mozlando meeting notes

Thanks to everybody for a fantastic workweek! I was impressed by how well we did having a lot of hard conversations about long-pending architectural changes, drilling into the open issues, and determining the next steps to evaluate possible solutions. I've attempted to format the notes from these m

[dev-servo] 15 concurrent Travis builders for the Servo GH organization

As of today, the Servo GitHub organization has been upgraded to support 15 concurrent jobs on Travis CI. Previously, it had the default for open source projects of 4, so hopefully this will help with our usage of services such as https://nightli.es, the early PR testing, and for all of the autoland

Re: [dev-servo] Error in Building Servo on Fedora 22 32 bit

Yes, please do let us know if this issue happens on a clean build, too! Unfortunately, we don't test 32-bit linux builds in our continuous integration so it's possible that something broke it (though I'd have hoped that 32-bit Android linux would catch it!). - Lars On Wed, Dec 2, 2015 at 3:56 PM,

[dev-servo] Meeting Nov. 30 (Mozlando topics; NCSU; crate squatting issues; PR queue)

https://github.com/servo/servo/wiki/Meeting-2015-11-30 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

[dev-servo] Rust upgrade landed!

After several weeks of grueling work by several people (including Manish, Simon, Matt, and many others, *especially* on projects where we are not maintainers) to push through all of the necessary updates to dependencies, the Servo Rust upgrade has landed! This upgrade is a major shift for Servo,

[dev-servo] Weekly meeting (Intermittents; mailing lists vs. discourse; libc; E-Easy issues)

https://github.com/servo/servo/wiki/Meeting-2015-11-16 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

Re: [dev-servo] PSA: Review delegation enabled for homu

> On Nov 11, 2015, at 8:31 PM, Bobby Holley wrote: > > On Wed, Nov 11, 2015 at 4:22 PM, Lars Bergstrom wrote: > I've been assuming the only time that we would use `delegate` is for > people like you (Bobby), whom we trust, but who have not gone through > the process to

Re: [dev-servo] PSA: Review delegation enabled for homu

Indeed, thanks Manish! I've been assuming the only time that we would use `delegate` is for people like you (Bobby), whom we trust, but who have not gone through the process to become a Servo reviewer. Honestly, I'd rather not have this feature at all --- I would prefer that a reviewer (even if it

Re: [dev-servo] 2015/11/09 meeting (GitHub config; servo.org landing page; workflow; homu magic)

On Tue, Nov 10, 2015 at 5:30 AM, David Bruant wrote: > Google Spreadsheet has a nice feature that allows sharing by URL in a > read-only fashion. More details here : > https://support.google.com/drive/answer/2494822 > Section "Share a link to a file or a folder", then "Computer" > (It's "Get share

[dev-servo] 2015/11/09 meeting (GitHub config; servo.org landing page; workflow; homu magic)

https://github.com/servo/servo/wiki/Meeting-2015-11-09 Bonus meeting from last week on Oxidation (Rust/Servo in Gecko): https://github.com/servo/servo/wiki/Oxidation-2015-11-05 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.

Re: [dev-servo] Meeting notes 11/2 (review carry-over; test coverage; 2016 roadmap; rebase/autosquash; PR queue; debug logging; CSSWG reftests)

You can also see it here publicly: https://docs.google.com/spreadsheets/d/1HYoEo5Vx9XuFWFh_1zGWtT-pvebNqspY-PqbUzh3y7Q/pubhtml There's nothing private about it! I just gave up after a half an hour trying to figure out "how do I share this google doc so that everyone in Mozilla+a list of contributo

[dev-servo] Meeting 2015-10-26 (WebRender; testing; ipc-channel on debug; bors try)

https://github.com/servo/servo/wiki/Meeting-2015-10-26 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

[dev-servo] Turning on autoloader rebasing and/or autosquashing

Two long-requested features have just been added by barosl to homu (https://github.com/barosl/homu/commit/d7ad33a1d4158fc78da4d86c6318a2f0fc1970cc ): automatic rebasing and autosquash. I’d like to turn both on for t

[dev-servo] Meeting-2015-10-12 (mozlando, governance, review queue, reftests)

https://github.com/servo/servo/wiki/Meeting-2015-10-12 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

[dev-servo] Meeting notes 9/28 (Meeting time change; additional TWiS reporting; script crate rebuilds; webrender)

https://github.com/servo/servo/wiki/Meeting-2015-09-28 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

Re: [dev-servo] Reviewers

On Sep 1, 2015, at 4:57 AM, James Graham wrote: On 01/09/15 12:29, Tetsuharu OHZEKI wrote: >> Should we introduce some files which is like `OWNERS` file in Chromium >> tree, or write a document to wiki? > > If you want it in-tree — and that does have some advantages — it makes sense > to make i

Re: [dev-servo] Meeting notes 8/17 (UA string updates; Android; profiling on ARM)

On Tue, Aug 18, 2015 at 5:13 AM, Gervase Markham wrote: > On 18/08/15 01:36, Lars Bergstrom wrote: > > https://github.com/servo/servo/wiki/Meeting-2015-08-17 > > About the UA: if you find sites break because you are sending a UA and > it sniffs you badly (e.g. sites using E

[dev-servo] Meeting notes 8/17 (UA string updates; Android; profiling on ARM)

https://github.com/servo/servo/wiki/Meeting-2015-08-17 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

Re: [dev-servo] mac3

I’d prefer that we only move things to nightly that will not cause a tree closure in the event of failure. e.g., performance tests, valgrind runs, fuzzing, etc. If we also put CSS / layout tests or other things we decide are “too slow” onto nightly builders, we’ll have the worst of both worlds

[dev-servo] Meeting notes 7/27 (critic, e10s, hyper, builders)

https://github.com/servo/servo/wiki/Meeting-2015-07-27 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

Re: [dev-servo] Proposal: Close areas of the tree that are yet to be e10sified

What is left to land these patches, and whom do you need help from to get these finished? I’m fine with freezing these interfaces if it’s for a week or so, but during the last few weeks this change has uncovered some pretty big holes in Cargo, the WPT tests, our CI configuration, etc. I guess I

Re: [dev-servo] Meeting notes 7/13 (ms2ger, surrogates in DOM, panics, IPC)

translate them into Traditional Chinese. (And perhaps also publish them in Mozilla Taipei's Chinese blog <http://tech.mozilla.com.tw/>) Cheers, Shing 2015-07-14 2:12 GMT+08:00 Lars Bergstrom mailto:larsb...@mozilla.com>>: https://github.com/servo/servo/wiki/Meeting-2015-07-13 &l

[dev-servo] Meeting notes 7/13 (ms2ger, surrogates in DOM, panics, IPC)

https://github.com/servo/servo/wiki/Meeting-2015-07-13 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

[dev-servo] Meeting notes and slides from Whistler

Below are the notes from all of the meetings that the Servo team held with various platform teams: https://github.com/servo/servo/wiki/Whistler-Houdini1 https://github.com/servo/servo/wiki/Whistler-Houdini2

[dev-servo] Fwd: June 15 meeting notes (Whistler training; Research Assistants; SM upgrade; Servo multi-process)

Begin forwarded message: From: "Robert O'Callahan" Subject: Re: [dev-servo] June 15 meeting notes (Whistler training; Research Assistants; SM upgrade; Servo multi-process) Date: June 15, 2015 at 6:15:13 PM CDT To: Lars Bergstrom Reply-To: rob...@ocallahan.org > pcwalto

[dev-servo] June 15 meeting notes (Whistler training; Research Assistants; SM upgrade; Servo multi-process)

https://github.com/servo/servo/wiki/Meeting-2015-06-15 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

Re: [dev-servo] Best way to work on multiple branches concurrently?

I personally keep the cargo dirs separate because Cargo doesn’t deal well with two concurrent runs, and I’m frequently developing and building in the two different clones at the same time. You *should* be able to share the rust/cargo snapshot directory without major concerns, though. On Jun 10,

[dev-servo] June 8 meeting notes (Friend of the Tree; Whistler training; rust-geom; Cargo; graphics APIs)

https://github.com/servo/servo/wiki/Meeting-2015-06-08 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

Re: [dev-servo] PRs are now gated on csstests on linux

On Jun 3, 2015, at 3:11 AM, James Graham wrote: > > On 02/06/15 18:59, Jack Moffitt wrote: >>> The mac3 builder will continue to run css tests and will now become red >>> when the build fails. This will not block PRs though. >> >> Are they unreliable there? What is the reason for this difference

Re: [dev-servo] Meeting notes 6/1 (Critic; SpiderMonkey upgrade; Rust upgrade; Devops; Reviewable perf; Interns)

Related to reviewable, we have a few ongoing discussions with them on performance: General conversation on large reviews vs. Critic - https://github.com/Reviewable/Reviewable/issues/103 Letting individual commits hide other content might help - https://github.com/Reviewable/Reviewable/issues/104

[dev-servo] Meeting notes 5/18 (Glutin, embedding, Whistler, RTL status)

https://github.com/servo/servo/wiki/Meeting-2015-05-18 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

[dev-servo] Meeting notes 5/11 (Animations/Transitions; PR handling; Whistler; rust-in-gecko; image libraries; Rust upgrade)

https://github.com/servo/servo/wiki/Meeting-2015-05-11 ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo

Re: [dev-servo] Servo on Windows?

We have a tracking issue for the work that needs to be done: https://github.com/servo/servo/issues/1908 But it’s not something we’re actively working on right now. - Lars On May 7, 2015, at 11:46 AM, Benjamin Smedberg wrote: Is there a plan to get Servo working on Windows? Or what would it take

Re: [dev-servo] Tree frozen for rust upgrade

The Rust upgrade has landed! Thanks to everybody for jumping on the reviews and fixes so quickly so that we could land it and reopen the tree. - Lars On May 4, 2015, at 2:24 PM, Lars Bergstrom wrote: The tree is now frozen pending landing the current Rust upgrade, which will bring us to

[dev-servo] Tree frozen for rust upgrade

The tree is now frozen pending landing the current Rust upgrade, which will bring us to: https://github.com/rust-lang/rust/commit/551a7484cf01440ee84148ebd18bc68bd7c8 , just 5 days ago :-) Please feel free

Re: [dev-servo] Testing Reviewable for reviews

ll request. Thanks! 2015-04-15 6:15 GMT+09:00 Lars Bergstrom : > As was mentioned briefly in the meeting notes for this week > (https://github.com/servo/servo/wiki/Meeting-2015-04-13 > <https://github.com/servo/servo/wiki/Meeting-2015-04-13> ), we are trying a > new service

[dev-servo] Testing Reviewable for reviews

As was mentioned briefly in the meeting notes for this week (https://github.com/servo/servo/wiki/Meeting-2015-04-13 ), we are trying a new service, http://reviewable.io , for performing our reviews. This week, pleas

[dev-servo] Meeting cancelled this week

This week’s Servo meeting is cancelled. Also, full-timers please remember to fill out the weekly status updates form so that we don’t have to do something hideous like requesting people report it during the meeting: http://benjamin.smedbergs.us/weekly-updates.fcgi/

Re: [dev-servo] Servo team Q2 projects

We've committed to an alpha release by the end of the calendar year :-) We have an Android APK being built and published nightly, but I wouldn't want to point people at it until we have more testing around that build, an upgraded SpiderMonkey, and do some of the work on networking and resource l

Re: [dev-servo] Servo team Q2 projects

Here are some ideas we've been talking about on my team: - Figure out CSS WG reftest integration. Right now, there's a python/mercurial build process that turns XHTML files into HTML to run them and it's not clear how to either integrate that without a giant mess (even by servo build standards!)

Re: [dev-servo] Build flavors and defaults

won't merge any PRs that introduce warnings? On 25/02/15 00:12, Lars Bergstrom wrote: > Two questions about build flavors. > > 1) Should we change the default build type back from debug to release? > > When we made the switch to cargo, we changed to debug builds by defaul

[dev-servo] Build flavors and defaults

Two questions about build flavors. 1) Should we change the default build type back from debug to release? When we made the switch to cargo, we changed to debug builds by default, which made for some good “reduced build times” headlines, but has gotten me mail from externals evaluating Servo ask

[dev-servo] PRs are now gated on building on gonk

In addition to testing on Linux and OSX plus building from Linux targeting Android, we will now gate Servo PRs on also building on Linux targeting Gonk. Thanks to the initial work by Michael Wu and some great follow-up work by Manish, we now have pretty well-automated builds of Servo targeting G

[dev-servo] Updated snapshot without LLVM assertions available

If you updated to the latest Rust snapshot before Feb. 13th, please perform a `./mach bootstrap-rust —force` to pull down a new version of the snapshot binaries. Previously, we built our snapshots the same way that the Rust team does — Release build, but with LLVM assertions enabled. There was

Re: [dev-servo] Tree is closed to land the Rust upgrade

iew> :-) - Lars On Feb 10, 2015, at 9:34 PM, Lars Bergstrom wrote: Please do not r+ any more patches until this Rust upgrade has landed! We are very close, with just a bit of code left to review and a small issue to address: https://github.com/servo/servo/pull/4893 <https://github.com/se

[dev-servo] Tree is closed to land the Rust upgrade

Please do not r+ any more patches until this Rust upgrade has landed! We are very close, with just a bit of code left to review and a small issue to address: https://github.com/servo/servo/pull/4893 Thanks, - Lars ___

Re: [dev-servo] Moving deps to nightlies

I'm in favor of this - it's what I meant to propose at the weekly meeting, which I unfortunately had to miss. Hopefully down the road we can also get Servo's cross-compilate targets (ARM32, ARM64) into the Rust nightlies, at which point we could get out of the business of producing compiler sna

Re: [dev-servo] NCSU project brainstorming

In a tweet here: https://twitter.com/annevk/status/557086893402521600 There's a recommendation that a browser play around with letting XHR trigger busy indicators: https://github.com/whatwg/fetch/issues/19 I like the idea of also having some projects that experiment with new (small) potential we

[dev-servo] Cancellation of this week's Servo meeting

Mozilla’s US offices are closed today for the Martin Luther King, Jr. holiday, so we will not be having our Servo meeting this week. See you all next week! - Lars Also, jdm, ms2ger, and others are making fantastic work going through the upgrade of Servo to Rust 1.0 alpha! If you would like to h

Re: [dev-servo] PSA: Rust upgrade landed

On Jan 8, 2015, at 9:50 AM, Ms2ger wrote: > > Thanks to all who helped! > > Be aware that you need to ./mach clean before building (symptom if you > forget is rustc failing with > >> task 'rustc' panicked at 'assertion failed: end <= self.len()', >> /home/larsberg/rust/src/libcore/slice.rs:432

[dev-servo] Meeting notes from Mozlandia

Below are links to transcripts of our (very productive!) meetings with teams outside of Research during the Mozlandia workweek. Meeting with the SpiderMonkey team: https://github.com/servo/servo/wiki/Mozlandia-JS Meeting with Build peers on landing Rust code in Gecko: https://github.com/servo/se

[dev-servo] PRs are now gated on the Android build

Thanks to some heroic dependency patching by Glenn and Matt last night / morning, Android is building again after the last Rust upgrade! Since our Android builder is also working (http://build.servo.org/waterfall ), I have changed the infrastructure to perform

[dev-servo] 9/22 meeting notes (workweek; CI infra; new HTTP library; libgreen removal; html5ever; cargo issues; pointer issues; rust hi-pri issues)

https://github.com/servo/servo/wiki/Meeting-2014-09-22 Note that there is also a Servo blog where we post "This Week in Servo" with additional information about what has happened each week: http://blog.servo.org/ ___ dev-servo mailing list dev-servo@li

[dev-servo] Meeting-2014-09-08 (cargo; script compilation memory usage; blocking issues; android; sharegl; busy-waiting)

Meeting notes: https://github.com/servo/servo/wiki/Meeting-2014-09-08 There was no meeting on September 1, as that was the US Labor Day holiday. Some interesting PRs from the last two weeks: - Glenn added initial layout debugging support: https://github.com/servo/servo/pull/3206 - Simon added si

Re: [dev-servo] Recent Improvements to Functions like getClientBoundingRect

On Aug 28, 2014, at 9:26 PM, Cameron Zwarich wrote: > On Aug 28, 2014, at 5:45 PM, Clark Gaebel wrote: > >> Running this on Firefox takes 500 ns/iteration. Chrome takes 700 >> ns/iteration. >> >> Servo before [1] lands took 8100 ns! That's paying a lot (some would say too >> much) for a para

[dev-servo] Meeting-2014-08-25 (new intern; workweek location; Travis CI; cargo; libgreen; security data analysis; power measurements)

Meeting notes: https://github.com/servo/servo/wiki/Meeting-2014-08-25 Some interesting PRs from last week: - SimonSapin added an ACID2 reftest for us, since we've been regressing ACID2 fairly frequently (https://github.com/servo/servo/pull/2741) - Servo no longer has a Rust submodule, saving much

[dev-servo] Meeting-2014-08-18 (unsafe code audit; new lifetime rules; JS blog post; Servo vs. Firefox perf and power; bloom filter)

Meeting notes: https://github.com/servo/servo/wiki/Meeting-2014-08-18 Some interesting PRs from last week: - Dotdash found a Servo abuse of transmute, which is part of what led to the unsafe code audit discussion in the meeting this week https://github.com/servo/servo/pull/3102 ). - Simon shaved

  1   2   >