3.0 final release

[arkaitzgarro]

3.0 final release

[arkaitzgarro]

It occurred to me that the 1.x branch we are proposing to support Laravel ^5.5 <6.0 will introduce breaking changes in what should be a minor release (following semver). What do you think about release that as 2.x and moving these release to 3.x? The 2.x line will start the new Agent and provide pre-Laravel 6 support (to a reasonable extent) while the 3.x line will move the project features forward and provide Laravel 6+ support. That will prevent surprises for your current users and make it easier to communicate what release to use.

I agree. I will release 3.0 for now, and wait until we make sure 2.x branch work as expected on L5.5 applications.

[dstepe]

I think the removal of Guzzle is a BC for most people. It fixes a specific use case, but I don't see that it was previously reported, so the release notes should probably point out what most people will experience, a need to add a new dependency as part of the upgrade.

The only other thing that comes to mind relates to the jobCollector. If that was present in the previous release, would it not have exhibited the send failures reported in #57 and fixed in #77? It that was not in the previous release, then it should be added as a new feature.

[dstepe]

It occurred to me that the 1.x branch we are proposing to support Laravel ^5.5 <6.0 will introduce breaking changes in what should be a minor release (following semver). What do you think about release that as 2.x and moving these release to 3.x? The 2.x line will start the new Agent and provide pre-Laravel 6 support (to a reasonable extent) while the 3.x line will move the project features forward and provide Laravel 6+ support. That will prevent surprises for your current users and make it easier to communicate what release to use.

[arkaitzgarro]

I think the removal of Guzzle is a BC for most people. It fixes a specific use case, but I don't see that it was previously reported, so the release notes should probably point out what most people will experience, a need to add a new dependency as part of the upgrade.

Yes, this is a good point, I will make it part of the release note. Thanks.

The only other thing that comes to mind relates to the jobCollector. If that was present in the previous release, would it not have exhibited the send failures reported in #57 and fixed in #77? It that was not in the previous release, then it should be added as a new feature.

Correct, this is something that we also fixed 👍

[dstepe]

I'm working on what is now the 1.x branch. I may not be able to complete it today unfortunately, but hopefully tomorrow.

[arkaitzgarro]

I'm working on what is now the 1.x branch. I may not be able to complete it today unfortunately, but hopefully tomorrow.

You mean 2.x branch right? I will create a 3.0 release for L6 support and 2.0 for L5.5. Latest changes are be available on 2.x branch already.

[dstepe]

Well, yes. It was still named 1.x when I started. I'll get caught up. :)

[arkaitzgarro]

v3.0 has been released 🎉