Datasets:
willtheorangeguy
/
2021-Ship-It-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.8k
[2088.00 --> 2090.82] They are also publishing a calendar in advance.
[2091.16 --> 2107.80] And because they provide translations of the software, they also have to take that into account into their release engineering cycle to give time to translators to provide their translations.
[2107.80 --> 2111.32] That's one thing I like in what they do.
[2111.72 --> 2113.80] Another one is the Mesa library.
[2114.72 --> 2117.94] So the library you can use on Unix.
[2118.34 --> 2125.54] So it's a library providing 3D implementation of OpenGL, for instance, and all the new standards in that area.
[2125.54 --> 2128.66] And now it grew a lot and provides as well.
[2128.66 --> 2132.10] And user-owned parts of GPU drivers, for instance.
[2133.00 --> 2135.36] So this is a large piece of code now.
[2136.06 --> 2145.44] And what I like in their release engineering, so I don't remember if they follow fixed timeline or if they provide calendars.
[2145.44 --> 2149.76] But I like how they handle the patches.
[2150.22 --> 2163.38] Like a developer is working on a patch and he doesn't know if that patch will go into the next minor release or if that needs to wait for the next major release.
[2163.96 --> 2169.22] So they have someone like FreeBSD who is responsible to manage the release engineering.
[2169.22 --> 2173.10] This time he's not hired or paid for that work.
[2173.20 --> 2175.64] So it's on his free time, spare time.
[2176.74 --> 2180.22] Yeah, they are trying various ways to...
[2181.20 --> 2182.46] That was a few years ago.
[2182.68 --> 2185.70] So that probably settled since.
[2185.82 --> 2193.02] But they wanted to try several things on what would be the best way to make that communication possible.
[2193.24 --> 2198.02] Like a developer want that patch into the next stable minor release.
[2198.02 --> 2202.80] But it might not fit the timeline and so on.
[2202.94 --> 2207.70] So they tried tags in the Git commits.
[2208.20 --> 2214.10] I think they tried mailing list, a specific mailing list where people would post their patch and so on.
[2214.14 --> 2216.42] So I don't know what they choose in the end.
[2216.56 --> 2220.70] But yeah, I like how they explored various methods.
[2221.28 --> 2223.50] Do you know what I remember about this specific topic?
[2223.96 --> 2226.94] During one of our RabbitMQ team summits...
[2226.94 --> 2229.16] By the way, RabbitMQ is a distributed team.
[2229.42 --> 2232.74] As I mentioned, twice per year, we used to meet in a single place.
[2232.82 --> 2233.52] It used to be London.
[2233.68 --> 2236.52] So we had like an on-site, which was an off-site for some.
[2236.66 --> 2237.58] But anyways, it was an on-site.
[2238.32 --> 2243.68] And during these team summits, I noticed that your laptop had like a weird thing on its screen.
[2244.26 --> 2245.48] And you were saying, like I said,
[2245.48 --> 2247.92] JSB, I think your screen like needs replacing.
[2248.06 --> 2249.16] This laptop needs replacing.
[2249.28 --> 2250.86] And you were saying, no, no, it's okay.
[2251.04 --> 2253.04] I'm working on some graphics drivers.
[2253.42 --> 2255.42] And I don't quite have this like thing right.
[2255.50 --> 2257.08] So pixels were looking like a bit weird.
[2257.18 --> 2259.36] And I noticed the pixels started changing.
[2259.46 --> 2265.12] And I was like, oh, JSB, why did you have to bring like a developer graphics card?
[2265.26 --> 2268.50] And then like a development graphics drivers to the team summit?
[2268.64 --> 2270.06] Like now we can't code properly.
[2270.06 --> 2276.48] So then obviously I like would take up my laptop out and okay, let's get a properly tested and
[2276.48 --> 2279.18] properly running graphics card and the graphics drivers.
[2279.56 --> 2280.82] That was a fun one.
[2281.10 --> 2285.34] And then you told me about like, you know, your interest in developing graphics drivers,
[2285.34 --> 2286.66] which I thought was fascinating.
[2286.66 --> 2287.68] Like, how do you even do that?
[2287.72 --> 2288.94] I was like, whoa, maybe?
[2289.42 --> 2292.10] Little did I know that, you know, also like free BSD.
[2292.38 --> 2294.24] I have to thank you for my free NAS server.
[2294.64 --> 2295.56] How stable that is.
[2296.28 --> 2297.54] And a couple of other things.
[2297.66 --> 2299.20] So yeah, that is pretty important.
[2299.20 --> 2301.30] And I mean, it's the backups, right?
[2301.32 --> 2305.12] All the pictures before iCloud and before other services, I used to back everything up on
[2305.12 --> 2306.40] free NAS and it never failed me.
[2306.56 --> 2308.20] So there's something to say there.
[2308.56 --> 2309.76] ZFS has something to do with it.
[2309.94 --> 2312.54] Drives failed, but free BSD never failed me.
[2312.64 --> 2313.64] So I was very happy.
[2314.58 --> 2314.74] Nice.
[2314.84 --> 2315.46] That's good to know.
[2315.86 --> 2319.02] So yeah, that is good feedback for you.
[2319.64 --> 2319.88] Yes.
[2320.42 --> 2321.44] It wasn't 5.0.
[2321.58 --> 2323.16] It was, I think, 9, 10.
[2323.32 --> 2324.28] Actually, no, it was 11.
[2324.34 --> 2325.10] I remember that one.
[2325.42 --> 2327.70] 11 when I like started really depending on it.
[2327.76 --> 2328.36] It was great.
[2328.36 --> 2330.86] So that was a great few years of service.
[2331.52 --> 2331.78] Great.
[2332.80 --> 2335.00] And yeah, you mentioned the graphic drivers.
[2335.42 --> 2342.46] That's a nice topic around release engineering because it's one area where it's difficult to find the right balance.
[2342.46 --> 2347.64] In fact, because we want to ship, obviously, a stable operating system in the end.
[2347.64 --> 2359.74] And the Mesa library also wants to be stable for all end users so that it can render your desktop videos and video games.
[2359.74 --> 2368.90] But that's an area where the hardware and the new models are put in the market at a high pace.
[2369.08 --> 2375.62] The technology evolves a lot and the GPU is a very complex beast.
[2375.62 --> 2380.62] So on one side, you want to support the latest GPUs.
[2380.62 --> 2389.16] But because if a user today buys a laptop, he will go for the latest shiny one.
[2389.26 --> 2391.88] He won't choose the one released three years ago.
[2391.88 --> 2398.36] So you want to ship all those new drivers and bug fixes as soon as possible.
[2398.94 --> 2405.66] But it's very difficult because the drivers themselves are very complex.
[2405.66 --> 2417.96] So it's very difficult to test what you ship because no one has all the various graphic cards and GPUs and configuration in general.
[2418.14 --> 2420.52] So it's impossible to thoroughly test.
[2420.98 --> 2429.14] So yeah, it's very difficult to find the right balance between shipping often and shipping something stable.
[2430.30 --> 2434.66] And I don't think we find the right balance in FreeBSD either.
[2434.66 --> 2438.76] So now drivers are provided as packages.
[2439.22 --> 2442.74] They are not in the core anymore, the source code of FreeBSD.
[2443.10 --> 2444.46] So that improved a lot.
[2444.78 --> 2454.06] But yeah, it still has some issues from time to time to decide on when to ship a new version of that package.
[2454.62 --> 2460.00] I think the more you dig into this and the more you work with this, you realize that it's not as straightforward.
[2460.00 --> 2465.72] And everybody tries to make the best decisions they can given what they know, right?
[2465.76 --> 2469.28] I mean, no one is trying to purposefully ship broken software.
[2469.80 --> 2471.38] Sometimes it's really hard.
[2471.52 --> 2475.42] And it looks like people don't care or they don't think, but they do.
[2475.82 --> 2477.22] And it's really, really hard.