TripleA Needs Your Help - Call for 2.0 Beta Testers

LaFayette

There is a 2.0 lobby, you'll connect to it automatically when joining the lobby using a prerelease. The new lobby is written from scratch, really appreciate all the testing we can get!

LaFayette

For a sense of where we are, you can check the list of 'must-do' items:

https://github.com/triplea-game/triplea/projects/14

We want to find as much as possible - operation unknown unknowns! That list needs to grow more, there are bugs out there, find them! Report them!
https://github.com/triplea-game/triplea/issues/new

This is a golden time to make a really valuable contribution! Join the ranks of the unsung TripleA heros - find those bugs :smirking_face:

LaFayette

@All - If testing against lobby or bots, please download the very latest version. This morning we changed the network communication layer slightly.

prastle

@LaFayette Last test was using 2.0.18694

RogerCooper

I still can't see the console using 18701. Even with show console setting set to true.

LaFayette

Created a bug report for the console: https://github.com/triplea-game/triplea/issues/6211

Please create bug reports going forward. We want developers doing code work, not transferring bug reports. Furthermore, we hit scaling problem with developers doing this, if a developer does not and takes a vacation, then the bug report gets lost in forums (which is pretty bad as it feels reported, and effort was spent to report it, but it is not).

LaFayette

Now is a good time for a final testing push.

https://github.com/triplea-game/triplea/releases/tag/2.0.18786 has fixes for all really major issues. There are a few nice-to-have additions still landing, but barring any major issues we'll begin soft launch at the end of this week. I can't emphasize enough how right now is the best time for testing.

LaFayette

Assuming no issues are found, looks like we're on course for the beta to become a release as soon as this Friday! While I want the release to happen, I'm more cheering for testing to find something now so we don't find it later.

prastle

@LaFayette I will beat the drums slaps @beelee and a few others

beelee

@prastle
getting a slow start today. I'll dive in soon. Problem with being prepped up is all i do is eat, drink and clean lol

prastle

@beelee hehe

LaFayette

Please leave a quick comment if you get some testing in and do not find any problems. It would be useful to know if the recent lack of new issues is due a sheer lack of problems, or if we have yet to find them.

prastle

@LaFayette bit of playing and testing .. curious if the bad words section was also supposed to include numbers? since for example 88 did not seem to be accepted..

beelee

@LaFayette
I'll tyr the bot thingy now. forget it's git number but basically can't join bots. I'll post at git

prastle

@beelee Either way a simple ? to you bee do you think it is releasable as well? And work continues over time? It has my vote.

beelee

@prastle idk some stuff been fixed. Probably never get it all. FR it let it go we'll get more testers then

prastle

@beelee I agree

LaFayette

Any specific problems please raise as issues so we do not have to discuss all of them here. It's too much, it's like a tree with many branches, the threads are too much to follow from just a single trunk.

Regrettably users are not eager to upgrade. Probably the last 4 releases all had major problems we discovered after releasing. We need the testing effort, it really is painful. It's a legacy of TripleA that much of the code is not automatically tested so we are left trying to manually test what we can (which is actually not all that sufficient, but better than nothing). Hence, the testing effort/labor is really appreciated and helps out a lot!

SilverBullet

@LaFayette which one for mac users?

LaFayette

Mac OS download is the macos.dmg link