tensorflow/flutter-tflite

Future Maintenance and Updates for flutter-tflite

azazadev opened this issue · 3 comments

azazadev commented

Thank you for your work on the flutter-tflite package. However, I’m concerned about its future maintenance:

Last Update: The package hasn't seen updates since December 2023.

Potential Blockers: Without ongoing maintenance, there's a risk that this package might become a blocker for future Flutter or other package upgrades.

Pub.dev Issues: The package currently fails static analysis on Pub.dev, and dependencies are outdated. Keeping these up-to-date is essential for continued compatibility.

We understand that you may be busy with other projects, just as we are, but having a clear status on this package is crucial for us. This is the only solid package for integrating TensorFlow Lite with Flutter, and knowing its future will greatly impact our planning.

Can you please provide a clear answer on whether this package will continue to be maintained and updated? Having this information will help the community make informed decisions moving forward.

@PaulTR and other maintainers, please try to find some time to provide an answer on this.

sadaqatdev commented

Hi @PaulTR, could you please merge this branch? It has been tested and is stable with the latest Flutter SDK. Thanks!

PaulTR commented

Alright 0.11.0 is published.

As far as future maintenance plans - this is very much a community driven project at this point. If folks using it would like to also update it, that'd be awesome (which is what happened for this most recent fix, adding various OS fixes, and updating it after that 3 year pause when this was on a third-party repo). They'll have more hands-on experience and know what issues are there than I will for now (unfortunately). I'm basically jumping in to run terminal commands and publish when I can (compared to the previous setup of nothing happening for ~3 years).

  • 🎉3
azazadev commented

Alright 0.11.0 is published.

As far as future maintenance plans - this is very much a community driven project at this point. If folks using it would like to also update it, that'd be awesome (which is what happened for this most recent fix, adding various OS fixes, and updating it after that 3 year pause when this was on a third-party repo). They'll have more hands-on experience and know what issues are there than I will for now (unfortunately). I'm basically jumping in to run terminal commands and publish when I can (compared to the previous setup of nothing happening for ~3 years).

Thanks @PaulTR !!!!