Fosuserbundle: 2.0 stable release?
The SonataUserBundle folks have decided not to update their bundle to support Symfony 3.0 until FOSUserBundle 2.0 is stable.
Is there a release time frame for 2.0 stable?
mmucklo
All 22 comments
I will do it tomorrow.
We wanted to give time for the community to update translations (see #2419), but remaining locales will stay incomplete in the 2.0.0 release. We cannot wait forever for other locales.
stof
on 24 Feb 2017
Alternatively we could remove the incomplete translation files.
XWB
on 24 Feb 2017
@stof - Awesome, thanks!
mmucklo
on 24 Feb 2017
@XWB I was thinking about commenting translations that we changed in 2.0 rather than removing the translation entirely (many strings are still the same)
stof
on 24 Feb 2017
@stof Ok :+1:
XWB
on 27 Feb 2017
Are there any news about v2.0 stable release?
vladim1
on 27 Feb 2017
@stof any news so far?
mvhirsch
on 28 Feb 2017
@stof Is there anything I can do to help?
XWB
on 6 Mar 2017
@stof 2 weeks have already passed after announcement. Could you share any info, plans or problems about v2 stable?
vladim1
on 10 Mar 2017
@stof could you please finally tag 2.0 version?
jontorrado
on 14 Mar 2017
@XWB please, do something with this. One of the most used bundles and no one is answering.
jontorrado
on 15 Mar 2017
lenybernard
on 15 Mar 2017
Symfony 3 was released at the end of 2015, nearly 18 months ago. It seems reasonable to me that FOSUserBundle require Symfony3, developers using Symfony2 can continue to use FOSUserBundle 1.3, but I imagine that once FOSUserBundle 2.0 is officially released there will be a significant shift to Symfony 3, given how widely-used this is.
On another note, you can remove Propel from the github header, since Propel 2 is still in alpha and Propel 1 is officially unmaintained.
tacman
on 16 Mar 2017
maybe they want to wait until symfony4 is out in november to fully support symfony3. weird...
fodaveg
on 18 Mar 2017
@stof can you give an update? It's quite clear a lot of people and other packages are waiting for news here, and you did say 'I will do it tomorrow' 23 days ago...
I can understand something else intervened with that plan, but a bit of communication has never hurt anyone ;-)
devartbvba
on 19 Mar 2017
@stof How about just a note as to what's holding you back from releasing 2.0? You mentioned #2419 -- is that the only thing?
tacman
on 21 Mar 2017
@stof @XWB Can anybode give a note about what is going on here?
vladim1
on 22 Mar 2017
I've asked @stof yesterday for a status update
@acrobat remaining stuff is only identifying outdated keys in translations (not all of them have been updated by the community) to comment them in the release (better having it untranslated than translated with old placeholders which are not replaced anymore). But I was on vacations last week and weekends are busy currently (for non-development things)
So we could help him and send pr's to comment keys that are not translated for 2.0!
acrobat
on 22 Mar 2017
@acrobat Sure, feel free to open a PR :)
XWB
on 22 Mar 2017
How can we get what translations should be updated?
vladim1
on 22 Mar 2017
@vladim1 see #2419
dragosprotung
on 22 Mar 2017
XWB
on 29 Mar 2017
Related issues
flik
路
4Comments
DeveloperSlope3
路
5Comments
antoinemineau
路
5Comments
hermandinho
路
4Comments
soullivaneuh
路
6Comments
Most helpful comment
I will do it tomorrow.
We wanted to give time for the community to update translations (see #2419), but remaining locales will stay incomplete in the 2.0.0 release. We cannot wait forever for other locales.