Triplea: TripleA 2.2 Release

Created on 25 Jul 2020  Â·  12Comments  Â·  Source: triplea-game/triplea

I'd like to cut a 2.2 release next week or early the following so that players can pick up the latest bug fixes.

Discussion

Most helpful comment

I think a new release should be a priority because (a) it will hopefully lower the volume of already addressed bug reports evading the dedup function, and make it clear what issues persist, and (b) the improvements we've made to the bug reporting itself will come into play.

I don't think the debate over breaking compatibility with a small number of save games should delay things... if we release without the PR in question being merged, the status quo persists in relation to that issue, there's no regression from 365, and we have a known issue that we can document in the release notes. All the other benefits accrue. We can issue a "hotfix" via a point release if we don't want to increment the version number when this issue is resolved.

We also establish the principle that official releases are going to come at a faster pace than in the past, and typically be more incremental in their changes.

All 12 comments

This would not be a prerelease then ? But saves still work ? I know #7227 was gonna fix some stuff, specifically #7177 but had some compatibility issues. #7237 addressed them. Personally I think it best to bite the bullet and do trevan's pr. It's a recent update/engine change/ thingy. Better now than a year from now :) Fewer will notice now, if any, imo.

At any rate, on a side note, I'm still working on being able to test it.

I think a new release should be a priority because (a) it will hopefully lower the volume of already addressed bug reports evading the dedup function, and make it clear what issues persist, and (b) the improvements we've made to the bug reporting itself will come into play.

I don't think the debate over breaking compatibility with a small number of save games should delay things... if we release without the PR in question being merged, the status quo persists in relation to that issue, there's no regression from 365, and we have a known issue that we can document in the release notes. All the other benefits accrue. We can issue a "hotfix" via a point release if we don't want to increment the version number when this issue is resolved.

We also establish the principle that official releases are going to come at a faster pace than in the past, and typically be more incremental in their changes.

Has anyone had a chance to do some quick smoke testing of the latest code? I think we probably should cut 2.2 as soon as this Monday.

If it is not too much work, it would be great if this feature
https://forums.triplea-game.org/topic/2151/feature-request-reinstate-internal-dice-roller
could be (re-)included.

I think that'll need to wait till 2.3.

On Sun, Aug 2, 2020, 6:07 AM P@nther notifications@github.com wrote:

If it is not too much work, it would be great if this feature

https://forums.triplea-game.org/topic/2151/feature-request-reinstate-internal-dice-roller
could be (re-)included.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/triplea-game/triplea/issues/7246#issuecomment-667671973,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC6SZOKZO332WE6M2NH5AKTR6VQILANCNFSM4PHIQVRQ
.

7350 should be corrected before.

@panther2 I agree #7350 is important, though 2.2 is about baked. It'll perhaps take 1-3 weeks to get #7350 fixed, meanwhile 2.3 would go out in 3-5 weeks. We're not really going to see much of a timing difference. I would absolutely agree to wait on 2.2 if #7350 was going to be a new problem introduced in 2.2.

Just letting you know that I'm not sure if you forgot to unpin the issue (is there a way to have issues automatically unpinned when closed?).

@DanVanAtta Agreed, where do we list the issues to be fixed for 2.3?

@panther2 as separate github issue reports for each one.

All of the 2.0 and 2.1 error report uploads will be closed pretty soon so we can clear up the list and focus on the problems coming from 2.2. If it feels like the issues would get lost we can certainly discuss a labeling strategy or to create a 2.3 project which can also be used to link issues together (the project might be the best route actually rather than a unique label).

@DanVanAtta I just want to make sure that #7350 and especially this feature:
https://forums.triplea-game.org/topic/2151/feature-request-reinstate-internal-dice-roller
don't get lost when talking about 2.3.
There is not even an issue for the latter, as feature requests are supposed to be noted in the forum - and the current complexity of the issue-lists invites to oversee some, too ...

@panther2 A 2.3 project is created, #7350 is linked to it and there is a TODO card for the internal dice-roller item: https://github.com/triplea-game/triplea/projects/18#card-43902730

Was this page helpful?
0 / 5 - 0 ratings

Related issues

DanVanAtta picture DanVanAtta  Â·  5Comments

DanVanAtta picture DanVanAtta  Â·  6Comments

RoiEXLab picture RoiEXLab  Â·  3Comments

Cernelius picture Cernelius  Â·  8Comments

panther2 picture panther2  Â·  6Comments