2.5.0 Deployment...

[APBA GO Jeremy]

… did not work!

Despite our best efforts and planning, our production deployment today ran into an issue related to database size that prevented us from completing the deployment.

We need to optimize the database migration portion of the deployment and take another crack at it next week.

Apologies for the inconvenience.

Thanks,
Jeremy

[Bruce66]

@APBA-GO-Jeremy Should we clean up our team lineups, old collections, etc to help in the process?

[APBA GO Jeremy]

@Bruce66 That’s a very kind suggestion! I think we can work through it without resorting to that kind of community effort. We just had to see the problem coming in order to prep for it.

Thanks for thinking about it!

(And us).

Jeremy

[mariner]

What is 2.5 about? Is there anywhere to read about this update?

[mariner]

This post is deleted!

[APBA GO Jeremy]

@mariner Game engine refactor, Ohtani rule, three batter rule. It doesn’t seem like a lot in a sentence but it’s a lot of foundation work for the future.

Thanks,
Jeremy

[striker2550]

@APBA-GO-Jeremy , will it address any of the game play issues?

[APBA GO Jeremy]

@striker2550 Yes, but due to the refactor it may introduce new ones.

Thanks,
Jeremy

[APBA GO Jeremy]

Hey Everyone!

We will be deploying 2.5.0 on Monday, August 22nd around 8 a.m. EDT. Unfinished solitaire games older than one year must be completed before the deployment as they will be deleted.

A lot of people have used unfinished Solitaire games to review player cards when the new season data comes out (each year for the past six years), and we’re cleaning them out of the database to increase performance and keep costs down.

All games prior to August 16th, 2021 will be affected.

Please contact support if you have any questions.

Thank you!
Jeremy