I think that the way of working with Open Source projects, libraries, code,
etc. is different from working with proprietary software.
With open source you have the code the debug and fix it if necessary. The
dev team don't need support.
You have a community that will help, or you could hire
You need to define what you mean by support. In most cases open Source
components should be considered as „not commercially supported“ unless you have
a contract with a commercial entity which is willing to give you this
guarantee. Having said that, assuming all proper commons component have
Hi Gary,
Thank you for your response, and sorry for the crossposting, and the confusing
reporting this. I was a bit confused on where to ask this question.
Since we are doing an analysis of obsolescence plan of the whole softwares used
in one of our release, we need to track all the EOL
Hello,
I work for a long-term project which requires strong and stable technical
support for every software used.
I want to know how long you are providing technical support for the following
SW products:
- Commons-io 2.1
- Commons-beanutils 1.8.3
- Commons-codec 1.4
- Commons-dbcp 1.3
-
Hi Sergi,
[Please don't cross-post to all the lists on our CC]
There is no "expiration date" on our components. We are all volunteers here
and we put in our time and support where we best see fit.
In general, we are more likely to fix/support current versions. For
example, this means that if
