Answer the question
In order to leave comments, you need to log in
What tools do you use to keep track of the releases of PLs, Frameworks, Libraries and other software used in development?
Every day, all developers in one way or another use their programming languages, libraries, frameworks, deployment systems, configuration systems, builds, and other software.
The same is true for all these PLs, build systems, frameworks, libraries, etc. updates are coming out.
The question is. And how do you keep track of all this zoo (meaning the release of new versions of the software used for development and maintenance)? How do you find out about the release of new versions, features, bug fixes in the stack you use, because it’s quite difficult to keep track of everything, and release cycles for all products are different.
Answer the question
In order to leave comments, you need to log in
IMHO it all depends on the stack.
About language versions - generally nonsense - not so often a new standard / version of the language comes out.
Next - a simple rule - no minor updates, unless there is a fix of a critical bug for the project - it's easy to monitor - when there is a critical bug not from your side - you will find a way ;-) (at least many products have bug trackers
) most have one way or another auto-check for updates.
About frameworks - see above - also not the most frequent event, and even between projects you can go over and see the latest versions.
Basically, there is no magic bullet.
Using a browser.
In general, the implementation of certain features is primary, and the use of frameworks as a feature implementation is secondary. If you use so many frameworks that you do not have time to keep track of the releases of their versions by organizing automatic updates, you will stop developing, it will all the time be spent on ensuring the compatibility of the innovations of the frameworks with each other. And, most likely, you will not need these innovations, because. at the time of the start of the project development, they were not there and they were not taken into account in the work plan.
Guys, you don't seem to understand the question. It's not about that.
Here is an example. There is a stack: go, node.js, php, react+redux, docker, jenkins, ansible, consul, vault, etc. We omit frameworks, libraries in each project and other things. But there are still Linuxes on which all this is spinning and libraries in them that also need to be updated periodically, because sometimes very terrible vulnerabilities or bugs pop up in them.
The question is how to effectively follow all this zoo in order to be aware of at least the main events that take place in one way or another in each product? Maybe email newsletters? Or twitter? Or RSS feeds? Does anyone have their own solutions?
If you are responsible for the entire technical component in the company, you will have to keep track of the relevance of the entire stack anyway. As a rule, within the company, the stack is quite large, whatever one may say.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question