I'm not sure why this post seems fail merging automatically but the topic has been posted recently and received some attention.
> After almost ten years of development, we have the regret to announce that we will put an end to our Theano development after the 1.0 release, which is due in the next few weeks. We will continue minimal maintenance to keep it working for one year, but we will stop actively implementing new features.
Summarizing this as "dead" is not hyperbolic IMO.
Theano is a Python library. Software doesn't die once someone decides that the design and implementation stages are over and the project enters the maintenance stage. The software remains operational and in use, and if bugs are found they will be squashed. That's it.
And you know, before the first Thursday of September, when the final release was made and it would have been time for the next community planning meeting, three companies had already stepped up and committed to continue development.
People and companies are still using Deis, for better or for worse, and although the Deis core team are elsewhere working on more Kube-native toolings, the core "Workflow" tooling is now fixed in place and for some of us, its functionality is essentially complete. For others, development of the tools will surely continue as no vaguely similar competitor exists, and those teams' needs may have not even been imagined yet.
Do you know what I've found? It is really significantly easier for a casual like myself to work on Deis now that it is in maintenance; you can actually commit yourself to making a change that will take a good long while, and with your own limited resources, when you know that the platform has ceased to be a moving target. You don't need to track everyone's concurrent development efforts to keep your own contributions relevant, if those other development efforts have stopped.
If this project is important to you, then you should pledge to support it in whatever material way you can. The project team has committed to keep the lights on for you for at least a year, so if you ever wanted to be a maintainer for an open source project, there is no time like the present. So rally the troops and step up to the plate!
