8000 Thoughts about releases and bugs · Issue #18403 · symfony/symfony · GitHub
[go: up one dir, main page]

8000 Skip to content
Thoughts about releases and bugs #18403
Closed
@maximecolin

Description

@maximecolin

Hi everyone, I write this issue because I'm kind of bothered and suprised about how some bugs and BC breaks are easily introduced on almost each version of Symfony, especially on the form component.

  • 2.7 was released with major bugs in the form component.
  • In 2.8 I encountered a bug on CollectionType about entry_options option replacing options option but the prototype was still created from the options option.
  • 3.0.3 introduced a bug in the choice list. The choice value was not pre set anymore from existing form data. I found an opened issue and PR fixing it so I waited for the 3.0.4.
  • 3.0.4 fixed the choice list issue and boom, another bug, this time on the NumberType which doesn't cast its value to float. So all my float validation breaks. There is already a PR to fix it, but one more time I have to wait for the next version or install the dev master version.

And there are only some of them I can recall. I don't remember the last Symfony version I used without this kind of annoying and obvious bugs.

I'm not questioning the awesome work that Symfony contributors make, I know many of them contribute beside their own job. I know it's not an easy task to manage all that stuff. But my point is : I think there is a lack of checks and tests before a tag is released. These bugs are not edge cases, they concern basic functionalities of the framework used in a large amount of Symfony based applications and are easily detected.

Am I the only one to think that way ? Is the framework functionnaly tested somehow before each release ? What do you think about enforcing the tests on basic Symfony functionalities ? Could it be a good idea to write functional tests like Symfony WebTestCase or behat features covering basics use case with controllers, forms, validations, ... ?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0