Release v2.0

[jackiekazil]

Last release was v1.21
Prep v2.0 Release

• Identify anything that needs to be pushed thru/completed for the release
• Tag with milestone Release v2.0 #1707
• Update history
• Submit PR for merge
• Merge PR
• release

[jackiekazil]

@tpike3 I haven't been tracking as well as you.
Is this a minor or patch? Should we be going from 1.2.1 to 1.2.2 OR 1.2.1 to 1.3.

RE: Milestone - The milestone was called "next release" I renamed to v1.2.2, which we can change if you think it should be 1.3. Do the attached PRs look like everything between v1.2.1 & where we are now?
Wasn't 2.0 stuff merged in to main? (If so, we should just push for 2.0 out the door -- It is much easier than trying to separate the two.)

[rht]

There was 1 breaking change merged. I think we should merge the rest and push for 2.0.

[tpike3]

I forgot about the 2.0 merged stuff.. let's just do 2.0.

[jackiekazil]

Thank you @rht and @tpike3 -
Agreed! 2.0 it is!
I will start prepping.

[jackiekazil]

i updated the title of this ticket.
Also created this branch - https://github.com/projectmesa/mesa/tree/v2.0
First steps are to...

1. Identify anything that needs to be merged/pushed thru. Since this is a major release, it is important for us to do this. Is there anything that breaks Mesa that is close to being done that we can/should include in 2.0?
2. Tag everything in 2.0 with the milestone & untag anything that isn't getting included -- https://github.com/projectmesa/mesa/milestone/33

[rht]

We should deprecate grid[x][y], keeping only grid[x, y], so that the API is independent of the implementation detail, that it doesn't have to be a list of list (see #815). Either we go straight to removing it in 2.0, or create a deprecation notice, and then remove it in 3.0. It is safer to do the latter.

[tpike3]

We should deprecate grid[x][y], keeping only grid[x, y], so that the API is independent of the implementation detail, that it doesn't have to be a list of list (see #815). Either we go straight to removing it in 2.0, or create a deprecation notice, and then remove it in 3.0. It is safer to do the latter.

I agree, we should deprecate and then create the notice and remove in 3.0

[rht]

I think it's fine to keep grid[x][y]. NumPy supports it, and any other backends could be made to support it with a brief implementation.