Skip to content

Conversation

tpike3
Copy link
Member

@tpike3 tpike3 commented Sep 6, 2025

Update init to 3.3.0.dev per release process

Copy link

github-actions bot commented Sep 6, 2025

Performance benchmarks:

Model Size Init time [95% CI] Run time [95% CI]
BoltzmannWealth small 🔵 +0.6% [+0.0%, +1.2%] 🔵 -0.5% [-0.6%, -0.3%]
BoltzmannWealth large 🔵 -0.5% [-1.3%, +0.4%] 🔵 +0.4% [-0.8%, +1.7%]
Schelling small 🔵 -0.1% [-0.3%, +0.3%] 🔵 -0.5% [-0.9%, -0.1%]
Schelling large 🔵 -0.5% [-0.8%, -0.1%] 🔵 -1.2% [-2.6%, -0.1%]
WolfSheep small 🔵 -0.9% [-1.1%, -0.6%] 🔵 +0.3% [+0.1%, +0.5%]
WolfSheep large 🔵 -0.4% [-1.0%, +0.2%] 🔵 +1.4% [+0.8%, +2.3%]
BoidFlockers small 🔵 -0.9% [-1.5%, -0.2%] 🔵 +0.4% [+0.2%, +0.6%]
BoidFlockers large 🔵 -0.1% [-0.5%, +0.4%] 🔵 +0.7% [+0.4%, +1.0%]

@@ -24,7 +24,7 @@
]

__title__ = "mesa"
__version__ = "3.3.0"
__version__ = "3.3.0.dev"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be either 3.3.1.dev or 3.4.0.dev

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(or 4.0.0.dev, but I don’t think we’re planning that already, right?)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3.4 dev makes the most sense to me. 3.3.1 would be for bug fixes.

Is there also a 3.3 maintenance branch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants