About the deprecated libraries, is there an expiration time in the code?

Thanks for the question, @André Dienes Friedrich. The simple answer is no, there is no set expiration time. We like to keep deprecated features around as long as a good number of users are depending upon them in production. Some reasons why a feature would be removed are: keeping the deprecated library conflicts with important features of the replacement; it becomes too burdensome to support the deprecated one; or the deprecated one becomes a risk in terms of security or data integrity. That hasn't happened yet with the libraries you mention.

In addition to Raj comment. What usually happens is that the deprecated libraries and calls are replaced with redirects to the new implementation.