I can see that the problem was solved in master, but without a tag, it forces users to use dev@master.

is there any chance to get this tagged?

@stof Could you please tag a new version with the fix?

No tag?

@stof Could you please tag a new version with the fix?

+1 for tag please!

a Tag would be very much appreciated

Just a friendly reminder for @stof to tag a release :-)

I @stof can you tag a new minor version with the fix please ? 🎁 👍 🥇 🙏

It is so sad that me have to wait so long. This is very bad... 😒

A tag would be lovely!

@stof what is the hold up for new release? Could we help you with this somehow?

Tag pliz @stof !

Another request for a new tag! Please, @stof ?

Please @stof a new tag will be nice?

@stof, can we help you somehow to maintain this project?

@stof pleaaaaaaseeeeee...... tag it!

I know it's been a long wait, but please 🙏 try to understand that sometimes maintainers don't have time for their open source projects for some reasons.

I'm sure @stof will tag a new version when he's ready again to maintain this bundle. Please, have some patience. Moreover, not having a new version only means that you'll get some deprecation messages. It's not such a big deal. Thank you!

@javiereguiluz can I somehow help to maintain the project?

@JustBlackBird I don't know, but thanks for trying to help! @stof is the maintainer of this bundle, so he will decide if he needs a helping hand.

I know it's been a long wait, but please pray try to understand that sometimes maintainers don't have time for their open source projects for some reasons.

I'm sure @stof will tag a new version when he's ready again to maintain this bundle. Please, have some patience. Moreover, not having a new version only means that you'll get some deprecation messages. It's not such a big deal. Thank you!

with all due respect, tagging a new release or at least answering to 3 month old issues in a widely used bundle isn't that hard

The issue is that if developers get in the habit of ignoring messages (like the deprecation messages here) then it's easy to miss something that's more important. I think that 100% of my deprecation errors on a new Symfony 4.3 project are from this bundle, so was hoping to get rid of them (without changing stability and using dev-master). So just adding my voice to the chorus respectfully requesting a new version tag.

@stof ?

Same here, please find a way to fix this!

@stof please tag

repo is dead...

It appears @stof is ignoring this repo. There are many forks of this repo already is there a supported one?

Interested in this tag or maintained fork.

By the way, what’s the best pattern to handle this change while maintaining both Symfony <4.3 and ^4.3 compatibility?

Hi, after waiting for a while, I made my own fork antishov/doctrine-extensions-bundle, tested master branch and released it as v1.4.0.
I really like this bundle and think that it's very helpful, so I plan to maintain it. Next steps are:

• Fix issues from this repo
• Remove support of old PHP versions: 5.3, 5.4, 5.5
• Improve tests coverage
• Prepare it for Symfony 4.4
• Add support of PHP 7.3 and 7.4

@antishov respect for your decision. Let me know if you need any help.

Remove support of old PHP versions: 5.3, 5.4, 5.5

IMO, there's no reason to support PHP5 at all. I would propose only supporting php7.1+.

How about dropping support altogether for Symfony 2 and 3? That is, only support Symfony 4.3 and 4.4. Anyone who needs this bundle for those versions can continue to use the original repo, and they won't switch to this fork

The master branch of the bundle is in sync with Symfony master branch which contains a BC break. If you are using a 2.0.x version of Symfony, you need to use the 1.0.x branch of the bundle.

This line in the documentation has always made me think that this bundle was a relic. Thank for for modernizing it!

@tacman great ideas for a new major version, thank you!

FYI : symfony/symfony-docs#12332 (comment)

at least he is alive :)
symfony/demo#1029 (comment)

+1

Symfony doc (https://symfony.com/doc/current/doctrine.html#doctrine-extensions-timestampable-translatable-etc) now recommend to use https://github.com/antishov/StofDoctrineExtensionsBundle.

So I suggest to migrate to @antishov bundle instead to continue to use this dead bundle. Thanks @antishov :)

Thanks @Cocray ! I switched to the new repo and I get no more Deprecations!

For those looking to do the same: this removes the old bundle and installs the new one:

composer remove stof/doctrine-extensions-bundle
composer require antishov/doctrine-extensions-bundle

Awesome, thanks @Cocray !

thanks @ZaneCEO i used:

composer remove stof/doctrine-extensions-bundle --no-scripts
composer require antishov/doctrine-extensions-bundle

Otherwise i would get cache clear errors

1.4.0 is now released.