Doctrine Project

@doctrineproject

Consider contributing to our Patreon or take a look at other ways of sponsoring us

Planet Earth
Дата регистрации: сентябрь 2008 г.

твиты

Вы внесли @doctrineproject в черный список

Вы уверены, что хотите видеть эти твиты? Если вы просто просмотрите твиты, @doctrineproject по-прежнему останется в черном списке.

  1. Закрепленный твит
    18 мар. 2019 г.

    If you like Doctrine and want to support the project, consider supporting us on Patreon. Even $1 a month is appreciated. Thanks!

    Отменить
  2. 4 июл.

    Some of these are more complex, and if feel like tackling them make sure to ask questions and ping and/or on the Doctrine slack about them, so that you don't accidentally work into the wrong direction.

    Показать эту ветку
    Отменить
  3. 4 июл.

    Want to help with moving ORM 3 forward? We have organized a Github Project with PRs to backport into 2.10.x or 3.0.x from the old-prototype-3.0.x branch. You can help by re-creating these PRs against our current branches:

    Показать эту ветку
    Отменить
  4. 14 июн.

    Doctrine ORM 2.9.3 fixing some BC breaks in 2.9.0 and bugs with static analysis typehints:

    Отменить
  5. 31 мая

    Doctrine ORM 2.9.2 was released with an important fix relating to the new typed properties support and column/join-column nullability:

    Отменить
  6. 24 мая

    Doctrine ORM 2.9 is out with an Attribute Mapping Driver for PHP 8 and many other changes:

    Отменить
  7. 21 мая

    Doctrine ORM 2.8.5 was released with a few bugfixes and improvements:

    Отменить
  8. ретвитнул(а)
    15 мая

    New release: persistence library 2.2.0 with support for PSR-6 caches and proxy class name resolvers to reduce coupling to doctrine/common:

    Отменить
  9. ретвитнул(а)
    27 апр.

    Ever wondered how to phase out a project that is heavily used by others without breaking their code? Join our chat with to figure out how the plans to do that with Cache 2.0. Already have questions? YT:

    Отменить
  10. 19 апр.

    We have just released Doctrine DBAL 2.13.1 and 3.1.0 including among other things important improvements to forward compatibility between both:

    Отменить
  11. ретвитнул(а)
    16 апр.

    Abracadabra! In just one small PR, doctrine/orm is now at and level 5 🪄 Ok, we cheated! Please send PRs to help us reduce our huge baseline files 🙏

    Отменить
  12. 6 апр.

    The 2.8.3 release is now marked as insecure as per FriendsOfPHP/security-advisories - so that hopefully tooling will notify users to upgrade to 2.8.4

    Отменить
  13. 6 апр.
    Показать эту ветку
    Отменить
  14. 6 апр.

    We released Doctrine ORM 2.8.4 with a critical fix to revert a regression in DQL query builder generation that slipped into 2.8.3. ->andWhere() parts with lower-case or/and were not properly parenthezied anymore. It is *strongly* recommended to upgrade if you are on 2.8.3

    Показать эту ветку
    Отменить
  15. 1 апр.

    We released Doctrine ORM 2.8.3 now - Most notably it includes a fix for a BC break with DBAL 2.13

    Отменить
  16. 30 мар.

    We released Doctrine DBAL 2.13 to ease migrations to 3.0 with more forward compatbility, runtime deprecations and re-introduced PHP 7.1 + 7.2 support.

    Отменить
  17. ретвитнул(а)
    15 мар.

    Released: doctrine/rst-parser 0.3.1 ! Thanks and for the nice contributions! Release notes:

    Отменить
  18. ретвитнул(а)
    15 мар.

    Yesterday released doctrine/migrations 2.3.3 and 3.1.1 which makes the package usable for users that work with MySQL and PHP 8 More details at and

    Отменить
  19. 17 февр.

    Doctrine ORM 2.8.2 released with a few bugfixes:

    Отменить
  20. 4 дек. 2020 г.

    doctrine/orm 2.8.1 is now out, fixing two regressions. Thanks for the eager testers and reporters of these problems.

    Отменить
  21. 4 дек. 2020 г.

    We released doctrine/orm 2.8 with PHP 8 support today and 2.7.5 that is rolling back two changes that accidentally allowed illegal mappings with association overrides and inheritance.

    Отменить

Загрузка может занять некоторое время.

Вероятно, серверы Твиттера перегружены или в их работе произошел кратковременный сбой. Повторите попытку или посетите страницу Статус Твиттера, чтобы узнать более подробную информацию.

    Вам также может понравиться

    ·