Phoenix: Maintenance/end-of-life/security updates policy?
One was recently added to Elixir itself: https://github.com/elixir-lang/elixir/issues/7489
Is there such a thing for Phoenix? Could one be added, or would it at least be possible to get an informal idea in a comment on this ticket?
henrik
All 4 comments
@chrismccord Hi! We happened to discuss this at work today, so just wanted to check if there are any news. Completely understand if it's not at the top of the priority list of course :)
henrik
on 7 Jan 2019
Yep, this would clear some worries for companies wanting to rely on Phoenix. I asked on mailing list to no vein.
In my opinion saying the project does not yet have a core team to handle it is completely fine. We all understand it, but being silent is weird and looks like the project is abandon (which is far from the truth looking at LiveView etc).
@chrismccord this is now a one year stale issue.
strzibny
on 3 May 2019
In my opinion saying the project does not yet have a core team to handle it is completely fine. We all understand it, but being silent is weird and looks like the project is abandon
We've had two Phoenix releases in the last month, with the latest less than a week ago. Our issue tracker tracks outstanding bugs and TODOs, of which this one is still on my plate. I need to plan these policies while coordinating with the Phoenix team on our commitments and availability to support older versions, which takes time and effort that has to be balanced with all the other work we are doing.
@chrismccord this is now a one year stale issue.
I'm aware of how long our issues are open for, so pinging to remind me only adds noise to my inbox. We have just 16 open issues at the moment, so this one in particular has not slipped my mind, but it's lower priority than others. I understand this issues is important to you and other folks, but please be patient :)
chrismccord
on 6 May 2019
Thanks for the reply and I am very sorry for adding the noise. Even a reply such as this one is helpful (there just wasn't any reply to both mailing list issue and this issue). If someone is a manager evaluating Phoenix they might find these issues instead of the frequent releases.
Anyway thank you for an update and for your work on Phoenix. I only have a success of Phoenix in mind and it was not to "complain".
strzibny
on 6 May 2019
Related issues
imranismail
路
4Comments
chrismccord
路
4Comments
cwisecarver
路
3Comments
oliverandrich
路
3Comments
noam87
路
3Comments
Most helpful comment
We've had two Phoenix releases in the last month, with the latest less than a week ago. Our issue tracker tracks outstanding bugs and TODOs, of which this one is still on my plate. I need to plan these policies while coordinating with the Phoenix team on our commitments and availability to support older versions, which takes time and effort that has to be balanced with all the other work we are doing.
I'm aware of how long our issues are open for, so pinging to remind me only adds noise to my inbox. We have just 16 open issues at the moment, so this one in particular has not slipped my mind, but it's lower priority than others. I understand this issues is important to you and other folks, but please be patient :)