Can we get a new release soon please

[vesper8]

@escopecz Sorry to bother you but there have been 95 commits since the last release over a year ago and now this logger issue is causing a lot of trouble for people who have upgraded to Laravel 10. Any chance you could tag a new release soon pretty please?

Many thanks!!

[escopecz]

@mollux do you want to get something else in or can we tag v4.0.0?

[mooror]

I would also request a new release as we are experiencing 8.1 strlen() null errors that I believe may have been fixed in issue #293 but are yet to be released (but please correct me if I am mistaken)

[bradjones1]

Who's the current primary maintainer of this package? A new release tag would be amazing.

[broskees]

Overriding classes currently, would also love a new tag. Thank you!

[RCheesley]

Hi folks! I've set up a milestone so you can see what we are hoping to include in the 4.0.0 release.

Your help would be very much appreciated in testing - this can be done using DDEV which sets everything up for you, check the readme for more guidance. Any PR with 'ready to test' needs to be tested. Thanks in advance! 🚀

[jhm-ciberman]

+1 to get a new release. Currently this is blocking us from integrating Mautic in our company.

[RCheesley]

@jhm-ciberman there's one PR waiting for testing in the milestone. Please test it and leave a review, and we can ship a release. Test instructions are in the readme, and you can also read https://contribute.mautic.org/contributing-to-mautic/tester#leaving-your-review for how to leave a review on the PR. Thanks!

[jhm-ciberman]

Hi @RCheesley! Sadly I don't have the knowledge required to review the PR since this is the first time we are using Mautic in our company and this is the first time I use Mautic too.

In our company we are just starting to integrate Mautic to our backend infrastructure, but we haven't started yet since #286 is blocking us from integrating mautic/api-library with our Laravel Backend via https://github.com/swisnl/laravel-mautic. (See swisnl/laravel-mautic#39 (comment)).

I would love to contribute to the project, however I don't feel familiarized enough with Mautic in order to review this particular PR. However, as far as I understand, this PR is a new feature, not a bug fix or even a breaking change. So it can be easily released on a next minor release cycle (e.g v4.1.0) after it's carefully tested and reviewed. The PR only adds an extra class (Mautic\Auth\TwoLeggedOAuth2) without modifying any existing public API. Since that is not a breaking change, it could be released on any minor release without breaking SemVer compatibility.

However, a lot of PRs and fixes currently included in v4.0.0-beta are blocking (Not only for me but for other package consumers too). It would be a shame that all the hard work made by the contributors with those fixes gets delayed because a single feature PR is blocking the release.

If this PR is really necessary in order to release, I could check in our company if we can reach some mautic developer with more experience to review that PR, but I think that's unlikely since it's our first time integrating Mautic.

Sorry if this sounded demanding. I know Open Source can be stressful with all people demanding things but not collaborating to the project. If there is any way I can help, please let me know.

Thanks! 😄

[mooror]

@jhm-ciberman Well said.

[escopecz]

@jhm-ciberman thanks for your understanding the challenges. The release was made as a beta: https://github.com/mautic/api-library/releases/tag/4.0.0-beta

Is there some problem to use that via Composer? Or what is the blocker?

I'm trying to understand the urgency here.

[Israel-Laguan]

@escopecz I suppose the "urgency" is more like "release the other features/fixes" in the milestone 10, check here the release have 26 PRs that includes bugs that maybe some consumers are facing since 2022.

@RCheesley I concur with jhm-ciberman that the PR #269 can be removed as a milestone member for v4, then added in the next cycle.

[escopecz]

@Israel-Laguan sure thing. We could release the PRs we have in the 4.0.0-beta as 4.0.0 (stable). Is that what you are saying?

Also, we are looking for maintainers of this repo. As you can see the core team is focused on the mautic/mautic repo and others are sidetracked. Anyone excited to step up and move this library to another level?

[Israel-Laguan]

Yes, that would do the trick!

About the library in my company we are just recently checking mautic as a marketing solution, in fact I am doing the MVP integration right now. I definitely will be around next months and contribute as much as I can!

Something to consider anyway is, what options do you have for contributing? For example do you have bounties system? I can sponsor some bounties. Also we can help bug reporting and code review.

I hope more people would participate in this great project!

[RCheesley]

Thanks @escopecz for picking this up and to everyone for the help in getting things moving forward. It'll be great to see a General Availability release. @escopecz I do think we should put out an announcement on social media / email, it's a major release after all cc @mautic/marketing-team-leaders for visibility. I wonder if it makes sense to do it right before the General Availability of Mautic 7, or to do it at the same time?

Indeed @Israel-Laguan we'd love to have more people helping us with maintaining the API Library and relevant documentation as well, so if you're able to help then take a look at https://mau.tc/contribute - we'll also get the contribution docs updated here so that it's clearer how to do so for this repo specifically - cc @mautic/education-team-leaders for visibility. I think the DDEV setup will also need addressing on this repo, as it's been a long time since we gave that some attention and I expect there's some changes we need to make for it to run properly.

We do have a bounties system: https://contribute.mautic.org/en/latest/contributing/mautic_bounty_programme.html - we use Open Collective to 'hold' the bounties pot and the core team are able to decide which issues get given a bounty to work on. If there are specific things you would like to see worked on and can financially support, please let us know and we can work out the best way - whether to do a spot bounty, or make it a project/initiative depending on the size/scale, and to get core team agreement on the task/s.

If you're not yet on Slack, please head to https://mautic.org/slack and we can chat further there!