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

New release planned: 4.0.0 #418

Closed
CarliJoy opened this issue Feb 5, 2024 · 8 comments
Closed

New release planned: 4.0.0 #418

CarliJoy opened this issue Feb 5, 2024 · 8 comments

Comments

@CarliJoy
Copy link
Contributor

CarliJoy commented Feb 5, 2024

The last release is almost two years old.

Is a new release planned?

@alexanderankin
Copy link
Collaborator

If this is just asking when it will happen, we are working on it in #405 , #408

@CarliJoy
Copy link
Contributor Author

CarliJoy commented Feb 5, 2024

Thank you for your efforts in creating an release/maintaining this project!
The link to the issue is enough for me.
I would suggest to leave this "issue" open as long there is no new release so people with the same question can be pointed to the correct "blocking issues".

@totallyzen totallyzen pinned this issue Feb 10, 2024
@totallyzen
Copy link
Collaborator

@CarliJoy hey! In fact I pinned your issue so folks can see. 🙂 Thanks for the interest in the project!

Once we're out of the woods with building and testing (see #408) the pace of changes should pick up a bit.

@alexanderankin
Copy link
Collaborator

hopefully we can get linting in here and docker compose either the old one or the new one (#400 (#362) or #426) - and we can do things like fixing the situation with reaper (#314) for 4.1 - also fairly high on my list is in general waiting strategies and in particular the vast array of dependencies for things like postgres that not everyone needs (todo find this one but its fairly obvious what to do - copy tc-java's way - waiting for logs most of the time) - not sure if im missing anything

@totallyzen
Copy link
Collaborator

hey, so I've got a working PR that I have confidence in -> #429

Release please can still be instructed manually to create new release PRs (via local CLI calls that create release them) for the usage of release-candidates, but it also should improve future release stability by not requiring individuals to release.

@totallyzen
Copy link
Collaborator

we have a release PR, but we don't have all the changes needed yet.
release PR -> #433 -> will update to 4.0 once we have #426 merged

This was referenced Feb 29, 2024
@alexanderankin
Copy link
Collaborator

please try out the new version!

@totallyzen
Copy link
Collaborator

@totallyzen totallyzen unpinned this issue Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants