Create a GitHub milestone for version 5.0?

[Nezteb]

I'm excited to see Partisan 5.0! As of this writing, we're on release candidate 15.

I was curious what remaining issues need to be worked on for the 5.0 release, but wasn't sure what was still required.

Regarding project organization, I was wondering how difficult it would be to set up GitHub milestones to attach issues to: https://github.com/lasp-lang/partisan/milestones

It would be nice to see which open issues I might be able to contribute to based on their priority for the 5.0 milestone. 😄

[aramallo]

Hi @Nezteb ,

There is only one outstanding issue with Hyparview that I still need to nail down which is due to Hyparview's rapid churn in membership. At the moment this causes a Test Case to fail and my target with 5.0 was for all original tests suites to pass.

I was just thinking about this, as I am already starting to plan v6.0 which would drop support for OTP 24/25. So I think we should release v5.0 this month, whether I find the issue or not.

Let me check Github milestones later today and I'll get back to you.

BTW, I would love to understand how are you using/planning to use Partisan.

[Nezteb]

I've been playing around with deterministic simulation and think Partisan fits well with the paradigm. 😄

Specifically I'm interested in the fault-injection capabilities (which I can't find docs on).

[aramallo]

@cmeiklejohn, who originally wrote Partisan as part of his PhD Thesis, started his work on fault-injection (Filibuster) in Erlang/Partisan but then moved to Python and Java. Check it out at https://www.filibuster.cloud

I am afraid the original Filibuster Erlang libs are no longer alive.

In Partisan you have the possibility of doing "interpositions" at the Peer Service level to delay, mutate or drop messages, but I haven't been using them at all (and thus why they are not documented)