When will the new official release come?

[zhiqiangdon]

Currently, the official release is still 0.6.12 from 3 months ago. What's the timeline of new release?

[rwightman]

@zhiqiangdon I have a few more models to update (push weights to HF hub) and a deprecation mechanism to add (to warn and remap model names that have changed from 0.6.x). I'm curently almost done updating swin, swinv2 and adding focalnet, after that the two most important models I want get updated (multi-weight support, weights on HF hub) before taking out of pre-release are regnet and resnet.

[zhiqiangdon]

Thanks @rwightman. autogluon.multimodal uses timm as an important dependency (https://github.com/autogluon/autogluon/blob/master/multimodal/setup.py#L35). Our users complain that they can't use the latest timm models after installing autogluon.multimodal. Looking forward to your new official release! Appreciate your efforts!

[rwightman]

@zhiqiangdon aside from the missing models, have there been any issues reported w/ 0.8 releases in autogluon, the main goal of the pre-release phase was for the adventurous people who used it, to report breaks so that I can have them fixed before I take it out of pre-release....

[zhiqiangdon]

@rwightman Everything looks fine. I would let you know if any issue is identified. One possible improvement is the documentation of models.

• There are currently many backbones in timm. Even the same model family, e.g. vit, has many models available. It would be better to give users some descriptions of what the backbone names mean. Many end users are not familiar with the papers. Giving them some intuitive introductions would help their usages.
• Some backbones name are not backward compatible. For example, vit_large_patch14_224_clip_laion2b is ok in 0.6.12, but no longer exists in 0.8.13.dev0. Adding some deprecation warnings and the new corresponding names would be helpful.

[rwightman]

For example, vit_large_patch14_224_clip_laion2b is ok in 0.6.12, but no longer exists in 0.8.13.dev0. Adding some deprecation warnings and the new corresponding names ... this is what I mean by deprecation mechanism. I itend to add a map that will map old names like that to the new forms w/ a warning BUT this is a bit of work to pull off and I didn't want it to block testing the new multi-weight form and models.