text stringlengths 0 1.8k |
|---|
[1058.48 --> 1060.28] Actually, I don't think I've ever told you this. |
[1060.78 --> 1065.22] So JSB is obviously the abbreviation of Jean-Sébastien Pedron, your full name, JSB. |
[1065.30 --> 1065.52] Yes. |
[1065.94 --> 1070.02] But G, G-S-P, is actually Jean-Saint-Pierre. |
[1070.40 --> 1071.92] And he's an MMA fighter. |
[1072.84 --> 1078.04] And, yeah, I used to do his workouts many years before I even met you. |
[1078.04 --> 1081.74] So whenever I say JSP, I'm thinking, ah, Jean-Saint-Pierre. |
[1081.90 --> 1083.22] And, like, I should go for a workout. |
[1083.60 --> 1084.90] So that's something which happens. |
[1085.66 --> 1086.72] I know you never knew that. |
[1086.78 --> 1087.90] But anyways, that was a tangent. |
[1088.40 --> 1090.10] So coming back, coming back. |
[1090.90 --> 1091.98] We were in Paris. |
[1091.98 --> 1102.64] And we had to, well, not figure out, but help this customer, this RabbitMQ customer, to make sure that RabbitMQ will be reliable in all sorts of scenarios. |
[1103.04 --> 1109.38] Because cars would end up not getting unlocked from their car key, from the remote car key. |
[1109.44 --> 1115.10] Because RabbitMQ is involved in between the car and the key, RabbitMQ is exchanging messages. |
[1115.52 --> 1116.98] And you wouldn't think about that. |
[1117.14 --> 1118.64] And neither should you. |
[1118.72 --> 1119.54] Why would you, right? |
[1119.54 --> 1121.78] People don't really care about these things. |
[1122.10 --> 1124.72] And when everything works, it doesn't matter. |
[1124.84 --> 1126.88] When it doesn't work, that's when the problems start appearing. |
[1127.14 --> 1130.90] So that was a very interesting conversation and meeting, I have to say. |
[1131.06 --> 1132.38] I enjoyed it greatly. |
[1133.22 --> 1139.96] And especially that RabbitMQ is often used to also mitigate problems on both sides. |
[1140.24 --> 1145.60] The application emitting the message and the application consuming it. |
[1146.30 --> 1147.06] That's right. |
[1147.36 --> 1147.52] Yeah. |
[1147.52 --> 1148.74] If you have a problem in the middle. |
[1148.74 --> 1154.78] Yeah, I'm pretty sure that today, for example, you have used a system that behind the scenes uses RabbitMQ. |
[1155.28 --> 1159.38] And that's why we think of it as core infrastructure, because we know that it's everywhere. |
[1159.84 --> 1159.96] Yeah. |
[1160.08 --> 1162.00] And it works well in most cases. |
[1162.30 --> 1165.90] But as it happens, we get to find out about all the cases when it doesn't work. |
[1166.16 --> 1168.48] And then we have to fix it and then ship those fixes. |
[1168.48 --> 1170.58] So that's a very interesting perspective. |
[1170.58 --> 1181.88] What's up, shippers? |
[1181.88 --> 1185.56] This episode is brought to you by our friends at Teleport. |
[1185.56 --> 1190.20] With Teleport Access Plane, you can quickly access any computing resource anywhere. |
[1190.66 --> 1198.22] Engineers and security teams can unify access to SSH servers, Kubernetes clusters, web applications, and databases across all environments. |
[1198.22 --> 1201.34] Teleport is open core, which you can use for free. |
[1201.34 --> 1207.22] And it's supported by their cloud-hosted version, which lets you forget about configuring, updating, or managing Teleport. |
[1207.44 --> 1209.16] The Teleport team does all that for you. |
[1209.42 --> 1213.84] Your team can focus on your projects and spend less time worrying about infrastructure access. |
[1214.44 --> 1217.90] Try Teleport today in the cloud, self-hosted, or open source. |
[1218.26 --> 1220.96] Head to goteleport.com to learn more and get started. |
[1220.96 --> 1222.96] Again, goteleport.com. |
[1232.32 --> 1243.40] So we've been talking generally about the RapidMQ release engineering, the FreePST one, how do they compare its projects, the whole core infrastructure notion. |
[1244.10 --> 1249.84] What I'm wondering now is, how does the FreePST release engineering process look like? |
[1249.84 --> 1264.22] So after that FreePST 5.0 disaster, the release engineering team started to work on something so that FreePST never faces that situation again. |
[1264.98 --> 1268.24] And that process evolved a couple times since. |
[1269.26 --> 1277.96] And today, the FreePST release engineering is based on a fixed interval between major releases, also minor releases. |
[1277.96 --> 1284.96] And we don't expect to start on a very specific day at 8 a.m., for instance. |
[1285.40 --> 1291.38] The OpenBSD one is sharp as a Swiss clock, but not in FreeBSD. |
[1291.62 --> 1301.08] When we want to start to prepare the next release, we have release engineers, so someone who is hired by the FreeBSD Foundation and is paid for that. |
[1301.08 --> 1310.38] He will take care of announcing to the FreeBSD contributors, but not only the contributors, but the entire community. |
[1310.92 --> 1319.00] He will publish a calendar where he will state that the code slush will begin at this date. |
[1319.34 --> 1320.74] Code freeze will be this date. |
[1320.74 --> 1325.10] We expect to cut the first beta at this date. |
[1325.10 --> 1332.16] We expect perhaps two betas, then two release candidates, specifying, again, the date. |
[1332.76 --> 1337.88] And he will indicate as well the date for the final release of FreeBSD. |
[1337.88 --> 1345.84] So that calendar is updated on a regular basis while we make progress in that release cycle. |
[1346.08 --> 1357.48] For instance, if we discover that there are bugs or there is a security issue or whatever the reason, we might want to delay beta for a couple days. |
[1357.48 --> 1363.76] Or we might want to add third or fourth beta or same for the release candidates and so on. |
[1364.12 --> 1374.70] So that calendar is very flexible, but it's quite useful because it tells to the FreeBSD contributors when to expect things. |
[1374.94 --> 1381.68] And it's very easy for contributors to organize and prioritize their tasks. |
[1381.68 --> 1394.60] For instance, if someone is working on some new features, then he knows that he has to finish by this date or it will be delayed to the next release. |
[1394.98 --> 1397.20] So that's very helpful for contributors. |
[1398.28 --> 1401.02] And like I said, this is not that strict. |
[1401.32 --> 1406.90] So any contributors can communicate also to the release engineer what he's working on. |
[1406.90 --> 1413.58] And so that the release engineer knows that, OK, this specific patch is incoming. |
[1413.86 --> 1419.24] It might introduce some instabilities, but we want that in the release. |
[1419.80 --> 1430.08] So he can anticipate that and perhaps tell anyone that, OK, we expect this to come in the next couple of weeks. |
[1430.42 --> 1434.06] This will go in that beta and we will add another one after that, for instance. |
[1434.06 --> 1446.28] So that calendar tool is really useful because it allows everyone in the community and the developers to communicate and understand what's going on. |
[1446.50 --> 1454.60] As I say, for users who will use that new version of FreeBSD, they can plan for testing, for instance. |
[1455.40 --> 1456.64] You mentioned Netflix. |
[1456.64 --> 1461.78] They appreciate that because they can test and invent the new feature. |
[1461.92 --> 1471.26] So they will fetch the development branch, for instance, compile FreeBSD and try it in their environment and see how it goes. |
[1471.34 --> 1473.14] They will give some feedback. |
[1474.40 --> 1486.56] So the fact that we use a calendar, a detailed calendar, yeah, it really helps the communication and makes the whole process more reliable and the outcome more reliable as well. |
[1486.64 --> 1491.66] So I think that's the main part which was introduced following FreeBSD 5. |
[1492.00 --> 1506.70] And we have some evolutions from time to time, but they are mostly around adjusting the timeframe between releases so that it's easy for end users to understand that, OK, this will come in next September. |
[1506.70 --> 1512.46] Perhaps the release will take a bit more time, but in next September, OK, we know that we'll have a new release. |
[1512.78 --> 1530.62] And this would have been very helpful in the time of FreeBSD 5 because we could have delayed some of the work done around locking to a future version, for instance, instead of trying to finish that huge task before shipping anything. |
[1530.62 --> 1532.76] Yeah, this is something. |
[1533.16 --> 1534.92] So first of all, this sounds really interesting. |
[1535.52 --> 1541.66] And what I'm wondering is, can users, sorry, could I see this calendar somewhere? |
[1542.08 --> 1543.92] Can I see how this process works? |
[1543.94 --> 1544.92] Is it publicly available? |
[1545.40 --> 1552.56] Yeah, the calendar is published on the FreeBSD.org website, announced on the mailing lists. |
[1552.76 --> 1553.14] OK. |
[1553.50 --> 1555.16] That's the main communication channels. |
[1555.46 --> 1557.88] And where does the FreeBSD development happen? |
[1557.88 --> 1561.58] I know that the RabbitMQ one happens on GitHub, but where does the FreeBSD one happen? |
[1562.36 --> 1581.30] Initially in CVS, I don't remember the years exactly, but at some point we switched to subversion and both servers were hosted internally in the FreeBSD infrastructure and in the Yahoo cluster in Sunnyvale. |
[1581.30 --> 1587.10] In the past year, we switched to Git, but we are still hosting that internally. |
[1587.32 --> 1590.64] And the reason is that we want to dock food FreeBSD itself. |
[1591.32 --> 1595.58] There are read-only mirrors available on GitHub. |
[1596.32 --> 1599.56] And there are still some discussions around that. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.