Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 2.3 #7927

Closed
DanVanAtta opened this issue Oct 18, 2020 · 6 comments
Closed

Release 2.3 #7927

DanVanAtta opened this issue Oct 18, 2020 · 6 comments
Labels
Discussion team communication thread, meant for coordination and decision making

Comments

@DanVanAtta
Copy link
Member

I think we can draw a line where we are and publish the next release. Does anyone know of anything we must fix before publishing 2.3?

The items that were in the 2.3 project are not necessarily must-do and will probably land at the same time if we release now and launch 2.4 in a month or two.

If anyone/everyone could spend some time doing regression testing, it would be really timely!

@DanVanAtta DanVanAtta added the Discussion team communication thread, meant for coordination and decision making label Oct 18, 2020
@trevan
Copy link
Contributor

trevan commented Oct 18, 2020

I think #7839 needs to be fixed before 2.3. It puts the game in a bad state and is really easy to encounter.

@trevan
Copy link
Contributor

trevan commented Oct 18, 2020

I think #7905 is a regression so that should probably be fixed before 2.3

@DanVanAtta
Copy link
Member Author

I think/hope both of those should be fixed by the in-flight PR. I should have been more clear, I think once the current set of PRs are merged, then we are perhaps at a good place to draw the line for 2.3

@panther2
Copy link
Contributor

@DanVanAtta

The items that were in the 2.3 project are not necessarily must-do and will probably land at the same time if we release now and launch 2.4 in a month or two.

Where are those listed? I can't find the list. I remember the "Internal Dice Roller" being one of the tasks...

@stale
Copy link

stale bot commented Nov 20, 2020

This issue has been automatically marked as stale because it has not had recent activity. If there is something that can be done to resolve this issue, please add a comment indicating what that would be and this issue will be re-opened. If there are multiple items that can be completed independently, we encourage you to use the "reference in new issue" option next to any outstanding comment so that we may divide and conquer.

@stale stale bot added the Stale label Nov 20, 2020
@stale stale bot closed this as completed Dec 20, 2020
@Cernelius
Copy link
Contributor

By the way, there is still "Release 2.4" open in projects.

@DanVanAtta DanVanAtta reopened this Aug 6, 2021
@stale stale bot removed the Stale label Aug 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion team communication thread, meant for coordination and decision making
Projects
None yet
Development

No branches or pull requests

4 participants