2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6
-
The bot-lobby (unintended) compatibility problem is described here: https://github.com/orgs/triplea-game/projects/2?pane=issue&itemId=18336902
This is the 2.6 project TODO list: https://github.com/orgs/triplea-game/projects/2
Notice that the details of the incompatibility issue are listed on a specific work-item card; and notably nobody needs to pull out the details from within a much longer conversation. In that vein, please make sure any problems you guys have mentioned are detailed on a work-item (ie: a github issue or a project card) and not just listed here where it'll be over-looked.
When this forum thread was initially created, it was meant to help coordinate amongst a larger group of people and at that time I was willing to help do the project management work of transferring any reported details to work-items. At this juncture we need help (someone else) to do that.
Bi-secting this problem would be a pretty painful exercise. We've got about 3000 changes or so since 2.5, which means we need to do around 12 iterations to get to roughly the right place where the regression was introduced. Each time a person has to install and launch a local lobby and launch a bot.
In light of this problem, 2.6 is no longer close. While having active and continuous help debugging any problems as 2.6 does progress is incredibly valuable, overall the release status right now is a deep shade of red. The incompatibility problem was found super-late in the process, it was found actually after even trying to launch 2.6 officially; and it's a major issue as it makes bot games unplayable.
-
@lafayette May you link where is that you get the information to make a file for hosting an automate host?
Also, I've no idea how to launch a local lobby.
-
@cernel At this juncture we would do well to have a dedicated thread for discussing the non-compat issue (lest we completely hijack this thread with just that one topic).
Though; I think that convo is probably short lived. Not only do you have to build a bot, you have to launch a database and build & run a lobby. If you really want to try, it's basically all of the steps when getting set up as a developer: https://github.com/triplea-game/triplea/tree/master/docs/development#developer-setup-guide
-
(I suggest editing the title of this topic - I mean the "Release Getting Close" part - as something more descriptive of the current release status.)
-
@cernel Fair point. My perspective is that this forum thread was meant to be active for just a few weeks. I'm not a big fan of a single long running thread to cover everything related to 2.6; as it's too complex to capture is a single conversation thread. Overall, we need to finish the 2.6 items, decide how to deal with the network regression; re-setup the 2.6 servers and then once again renew the beta testing. I somewhat think this thread can be locked/archived at this point.
-
@lafayette said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
I'm not a big fan of a single long running thread to cover everything related to 2.6; as it's too complex to capture is a single conversation thread
I need some time to reflect on this. It might be useful to have that single guiding thread to help give some direction. Though, the last thing I want to do right now is promise to do any more work beyond what is already a months long backlog. I think we might actually already have that very thread created some many months ago that summarized most of the changes that were going into 2.6 (it was a summary of the different things map makers had to be aware of). I suspect creating a new '2.6' thread is going to duplicate that.
Though to re-iterate for those skimming to the latest, the large-scale effort to do beta testing of 2.6 is mostly closed as a major regression was found and needs to be fixed before we can move forward.
-
@beelee said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
This goes to 2.5 Lobby https://github.com/triplea-game/triplea/releases/tag/2.6%2B14129
This goes to 2.6 https://github.com/triplea-game/triplea/releases/tag/2.6%2B14130
Hopefully this is of some use as Idk exactly what's required here
Put this in a git issue. https://github.com/triplea-game/triplea/issues/11499
-
Me and @Schulz played 1 round of 270BC Wars using the latest 2.6, me hosting privately. All was fine.
-
Just wanted to bump this.
I've been going through the bug tracker and fixing some remaining 2.6 issues. There's still a couple that I think we need to fix before 2.6 can be released, but in the meantime, I think it would be great if folks could give the latest prerelease a go and report any issues.
Thanks!
-
I do want to mention that I see upthread that we have a bot incompatibility release blocker. For sure we'll need to get that fixed, but I want to make sure we give the rest a spin and find any other issues before release.
-
@alexei-svitkine The inability to download new mods from GitHub is a big problem with 2.6. That needs to be fixed.
If have been posting all the mods created over the years to GitHub, and I will like to see someone else be able to play them.
-
2.6 is significantly faster than 2.5 and so great for playing against the AI.
-
@rogercooper map downloads should work. I just tried. Are you seeing problems?
-
@alexei-svitkine New mods are not appearing. I updated TripleA this morning.
-
@Alexei-Svitkine
Map Tags was meant to be a feature of 2.6 to aid with selecting a map file for download.I think it is ready for me to enter the Tags, is it? If so how do I do it?
Here is the link to the discussion, the last post is the most meaningful with prior posts by LaFayette describing what has been done already.
https://forums.triplea-game.org/topic/2801/map-tags-for-release-2-6/109?page=6
-
@alexei-svitkine said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
Just wanted to bump this.
I've been going through the bug tracker and fixing some remaining 2.6 issues. There's still a couple that I think we need to fix before 2.6 can be released, but in the meantime, I think it would be great if folks could give the latest prerelease a go and report any issues.
Thanks!
Play by Forum still is a huge issue. As long as the PBF logic doesn't keep track with the requirements of NodeBB it is a mess. 2.6 at any time introduced a fix to work with NodeBB 1.16, but with NodeBB 2.x and likely 3.x it is broken again.
One of the problems behind is that no one cares to update the forum software of this forum.
-
PBF being broken is unfortunate, but it's not a 2.6 bug, right? i.e. it's broken on 2.5 too, I assume. If so, it shouldn't block releasing 2.6.
For map tags, I'm not sure anything was implemented to support them yet? If so, again it wouldn't be a 2.6 thing.
My goal is to try to get 2.6 to a level where there are no regressions over 2.5 so we can just release it, making the stable version benefit from all the improvements over the last few years.
Then, we could still follow it with something like 2.7 that could focus on e.g. fixing PBF and adding map tags...
-
@alexei-svitkine said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
PBF being broken is unfortunate, but it's not a 2.6 bug, right? i.e. it's broken on 2.5 too, I assume. If so, it shouldn't block releasing 2.6.
For map tags, I'm not sure anything was implemented to support them yet? If so, again it wouldn't be a 2.6 thing.
My goal is to try to get 2.6 to a level where there are no regressions over 2.5 so we can just release it, making the stable version benefit from all the improvements over the last few years.
Then, we could still follow it with something like 2.7 that could focus on e.g. fixing PBF and adding map tags...
While you are right, of course, the problem is that taking care about this issue has been postponed with exactly your arguments again and again and again ....
For the PBF-community this compatibility is the most awaited feature.
This is not to offend you, I am happy that you came back to move things on.
-
@All
While I agree that 2.6+ has sat around for a while. I disagree with the need to "Release 2.6". 2.6 may run faster as pointed out by @TheDog, but there are no "Feature Request" added. There is no difference between coding for 2.5 and 2.6. Things that could have been added to 2.6 like checking for an AI player, checking the amount of resources, adding "count" to "resource", to name a few.
Adding such features, when requested by map makers, would allow that release to be tested. Not adding anything, means there is no reason to test future releases. Thus no "push" for that release.
These are my thoughts--
Cheers...
-
@alexei-svitkine said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
My goal is to try to get 2.6 to a level where there are no regressions over 2.5 so we can just release it, making the stable version benefit from all the improvements over the last few years.
Maybe it is worth to point out what the improvements really are, that players profit from .
I mean there have been countless merges of PR that certainly mean something to developers but are only cryptic for players.
Have there been changes with impact on game rules? Is there something to playtest against rules compliance? Have there been noteable improvements of gameplay?
What actually needs to be tested?Apart from of course welcome specific detail interests of map makers - are there any improvements for the playing communities that come with 2.6?
Being one of the few persons who were or maybe still are interested in trying to follow development I unfortunately got lost at an unspecific point in the past, personally.
