Skip to content

New release planned: 4.0.0 #418

Closed
Closed

Description

@CarliJoy

The last release is almost two years old.

Is a new release planned?

Activity

  1. alexanderankin commented on Feb 5, 2024

    @alexanderankin
    Member

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

  2. CarliJoy commented on Feb 5, 2024

    @CarliJoy
    ContributorAuthor

    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".

  3. pinned this issue on Feb 10, 2024
  4. totallyzen commented on Feb 10, 2024

    @totallyzen
    Contributor

    @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.

  5. changed the title [-]New release planned?[/-] [+]New release planned: 4.0.0[/+] on Feb 20, 2024
  6. alexanderankin commented on Feb 21, 2024

    @alexanderankin
    Member

    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

  7. totallyzen commented on Feb 27, 2024

    @totallyzen
    Contributor

    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.

  8. totallyzen commented on Feb 29, 2024

    @totallyzen
    Contributor

    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

  9. alexanderankin commented on Mar 6, 2024

    @alexanderankin
    Member

    please try out the new version!

  10. unpinned this issue on Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions