Closed mmucklo closed 7 years ago
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.
Alternatively we could remove the incomplete translation files.
@stof - Awesome, thanks!
@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 Ok :+1:
Are there any news about v2.0 stable release?
@stof any news so far?
@stof Is there anything I can do to help?
@stof 2 weeks have already passed after announcement. Could you share any info, plans or problems about v2 stable?
@stof could you please finally tag 2.0 version?
@XWB please, do something with this. One of the most used bundles and no one is answering.
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.
maybe they want to wait until symfony4 is out in november to fully support symfony3. weird...
@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 ;-)
@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?
@stof @XWB Can anybode give a note about what is going on here?
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 Sure, feel free to open a PR :)
How can we get what translations should be updated?
@vladim1 see #2419
The SonataUserBundle folks have decided not to update their bundle to support Symfony 3.0 until FOSUserBundle 2.0 is stable.
SonataUserBundle#768
Is there a release time frame for 2.0 stable?