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 there a fix done to commons-logging, currently at 1.2, it would be released in a future 1.2.1 or 1.3. If you cannot use 1.2 and you are stuck on 1.1.1, it is very unlikely that I would take the time to release 1.1.2. Mileage may vary for other volunteers. Gary On Tue, Nov 12, 2019 at 10:23 AM Comeche Nolla, Sergi < scome...@eservicios.indra.es> wrote: > 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 > - Commons-digester 2.1 > - Commons-logging 1.1.1 > > Please I appreciate so much that you can give me expiration dates for each > of these software products! > > Thank you! > Sergi > > ________________________________ > > Este correo electr?nico y, en su caso, cualquier fichero anexo al mismo, > contiene informaci?n de car?cter confidencial exclusivamente dirigida a su > destinatario o destinatarios. Si no es vd. el destinatario indicado, queda > notificado que la lectura, utilizaci?n, divulgaci?n y/o copia sin > autorizaci?n est? prohibida en virtud de la legislaci?n vigente. En el caso > de haber recibido este correo electr?nico por error, se ruega notificar > inmediatamente esta circunstancia mediante reenv?o a la direcci?n > electr?nica del remitente. > Evite imprimir este mensaje si no es estrictamente necesario. > > This email and any file attached to it (when applicable) contain(s) > confidential information that is exclusively addressed to its recipient(s). > If you are not the indicated recipient, you are informed that reading, > using, disseminating and/or copying it without authorisation is forbidden > in accordance with the legislation in effect. If you have received this > email by mistake, please immediately notify the sender of the situation by > resending it to their email address. > Avoid printing this message if it is not absolutely necessary. >
