This past week, there was no sync and no RFC activity and no big announcements. It was also a week that your author was very busy at work and so, put all that together and this week’s Last Week in Pony is a light one.
Last week, we accepted two RFCs that will result in changes to Pony syntax and the standard library respectively.
Not a lot of things that normally make up the content of Last Week in Pony happened this week. Both Sean and Joe were sick so there was no sync meeting which tends to have a cascading effect on other activity.
Most of the “above ground” Pony activity this week was our usual weekly development sync meeting and our weekly office hours.
The headline news of the week, if you are using Pony 0.52.3 to 0.52.5, you should update to 0.53.0 as soon as possible to address a runtime segfault.
The big news is that you should update your Pony version to 0.52.5. It’s very important if you are using Pony 0.51.2 to 0.52.3 that you update as soon as possible.
It was a week dominated by conversations about distributed cycle detection. Both the Pony development sync and Office Hours were almost entirely focused on the topic. Given the somewhat complicated nature of the topic, we expect that it will be a regular source of conversation for a while.
The big news for this week is that we merged and release a safety fix that can have a large impact on performance for applications that send lots of messages that need to be traced by the garbage collector. We’ll be incrementally adding back in performance as we make the compiler smarter.
Not a lot happened in the land of Pony this last week, but a lot will be happening soon.
It was a week of releases and CI changes. We’ve switched from FreeBSD 13.0 to FreeBSD 13.1. We’ve dropped Rocky 8 support (for now anyway). We released a new ponyc with a wicked important bug fix. We released a far less interesting version of corral. So, kids, grab a Moxie, put on some Johnny Cash and dig in. It’s that time again, Last Week in Pony time!