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

Some minor changes to prepare for the 2.3.8 release #279

Merged
merged 3 commits into from
Dec 12, 2024

Conversation

sanguinariojoe
Copy link
Collaborator

Just a couple of tweaks to launch the 2.3.8 release. Tomorrow I am still on the office. If we do not launch the missiles @RyanDavies19, we will have to wait until 12-dic (not really a drama anyway)

@RyanDavies19
Copy link
Collaborator

@sanguinariojoe this all looks good, could we change the filename to polyester.py to keep things consistent?

Also just to confirm, this python test is the same as the cpp test right? When I merge in the viscoelastic capability should the tests be put in both of these or is just the cpp one sufficient?

@sanguinariojoe
Copy link
Collaborator Author

@sanguinariojoe this all looks good, could we change the filename to polyester.py to keep things consistent?

I am afraid not. PyTest has the test_* naming policy (I suppose it can be done, but some hacking will be required that is probably backfiring on the future)

Also just to confirm, this python test is the same as the cpp test right? When I merge in the viscoelastic capability should the tests be put in both of these or is just the cpp one sufficient?

cpp is surely enough

@sanguinariojoe sanguinariojoe merged commit 4828499 into FloatingArrayDesign:dev Dec 12, 2024
9 checks passed
@RyanDavies19
Copy link
Collaborator

RyanDavies19 commented Jan 22, 2025

@sanguinariojoe was this intended to trigger a release? Trying to work through some bugs with the 2.3.7 windows DLL causing GH actions to crash on the WECSim tests (WEC-Sim/WEC-Sim#1400). I notices though we don't have any PR documenting the 2.3.8 release but the binaries are available.

@sanguinariojoe
Copy link
Collaborator Author

Nope. It is because master and dev diverged, so I did the release forcily pushing on master. See #278

@RyanDavies19
Copy link
Collaborator

Oh right, thanks for the reminder. I forgot about that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants