-
Notifications
You must be signed in to change notification settings - Fork 110
Archive repo #223
Comments
My gut feel is to keep this open until Symfony 3.4 is out of support, or at least out of maintenance (Symfony roadmap). The new fork only supports Symfony >= 4.3, so this repo may be needed for changes to the Symfony < 4.3 version. |
Ah, that makes sense. Fair enough. |
Just for reference, I actually did keep Symfony 3.4 compatibility in my 2.0 release (explicitly only 3.4, 4.4, and 5.x are supported; if you're needing one of the non-LTS Symfony versions then you'd need to stay on this bundle). |
Ah, thanks for clarifying @mbabker. Are you planning on supporting 3.4 in future releases or was it just the 2.0 release? If 3.4 will be supported in future, I might update the link to your fork to say "Symfony 3.4 or >= 4.4", and we can also think again about archiving this repo. |
I’ll keep 3.4 supported until Symfony EOLs it.
On Wed, Jan 29, 2020 at 4:09 AM Sam Partington ***@***.***> wrote:
Ah, thanks for clarifying @mbabker <https://github.com/mbabker>. Are you
planning on supporting 3.4 in future releases or was it just the 2.0
release? If 3.4 will be supported in future, I might update the link to
your fork to say "Symfony 3.4 or >= 4.4", and we can also think again about
archiving this repo.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#223>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACZ7IJRTQKT2GF4KSIU6Q3RAFIVDANCNFSM4KJFJ3KA>
.
--
- Michael Please pardon any errors, this message was sent from my iPhone.
|
Oh, cool, thanks. 4.3 is still receiving security fixes until July, so I think I'll probably keep this repo open until then, and then archive it. I've updated the text which links to your fork to include the right version numbers. |
Although I'm not going to archive this repo until next month as mentioned, I have marked the package as abandoned on Packagist, with a reference to |
Now that 4.3 is no longer supported, there's no reason to continue using this repo instead of the fork, so I'm going to archive it as suggested. |
Should we archive this repo in GitHub now that we have an active fork?
This will mean that users of this repo will no longer be able to open PRs and issues, or comment on existing ones.
@sampart how do you feel about this?
The text was updated successfully, but these errors were encountered: