Technical Support Expiration Date

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Technical Support Expiration Date

Comeche Nolla, Sergi
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.
Reply | Threaded
Open this post in threaded view
|

Re: Technical Support Expiration Date

garydgregory
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 <
[hidden email]> 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.
>
Reply | Threaded
Open this post in threaded view
|

RE: Technical Support Expiration Date

Comeche Nolla, Sergi
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 support for each software and make decisions whether to keep the version or migrate to new one, depending on longevity of the support given.

I understand that older version will have very limited support for your part, hence we should think about migrating to newer versions if we want support.

Thanks again for that.
Regards,
Sergi

-----Original Message-----
From: Gary Gregory <[hidden email]>
Sent: martes, 12 de noviembre de 2019 16:35
To: Commons Users List <[hidden email]>
Subject: Re: Technical Support Expiration Date

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 < [hidden email]> 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.
>

________________________________

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.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: Technical Support Expiration Date

Bernd Eckenfels
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 community support or the latest version only is a good start. This could mean you might need topfit bugs yourself, but you can submit them for upstream inclusion if they are applicable.

All projects you mentioned beside commons-logging are properly supported, for commons-logging is kind of sustained support, I can’t imagine anybody would use it for new projects.

Gruss
Bernd


--
http://bernd.eckenfels.net

________________________________
Von: Comeche Nolla, Sergi <[hidden email]>
Gesendet: Dienstag, November 12, 2019 4:40 PM
An: Commons Users List
Betreff: RE: Technical Support Expiration Date

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 support for each software and make decisions whether to keep the version or migrate to new one, depending on longevity of the support given.

I understand that older version will have very limited support for your part, hence we should think about migrating to newer versions if we want support.

Thanks again for that.
Regards,
Sergi

-----Original Message-----
From: Gary Gregory <[hidden email]>
Sent: martes, 12 de noviembre de 2019 16:35
To: Commons Users List <[hidden email]>
Subject: Re: Technical Support Expiration Date

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 < [hidden email]> 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.
>

________________________________

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.
Reply | Threaded
Open this post in threaded view
|

Re: Technical Support Expiration Date

Simon De Uvarow
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 someone from the
community to develop what you need. But I believe, it isn't the common case.

I think it's not usual to request technical support to the community that
supports an open source library.
You need to find a company if you need that.


"No olvides, no traiciones, lo que llevas bien dentro de ti. No olvides, no
traiciones, lo que siempre te ha hecho vivir."


On Tue, Nov 12, 2019 at 1:25 PM Bernd Eckenfels <[hidden email]>
wrote:

> 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
> community support or the latest version only is a good start. This could
> mean you might need topfit bugs yourself, but you can submit them for
> upstream inclusion if they are applicable.
>
> All projects you mentioned beside commons-logging are properly supported,
> for commons-logging is kind of sustained support, I can’t imagine anybody
> would use it for new projects.
>
> Gruss
> Bernd
>
>
> --
> http://bernd.eckenfels.net
>
> ________________________________
> Von: Comeche Nolla, Sergi <[hidden email]>
> Gesendet: Dienstag, November 12, 2019 4:40 PM
> An: Commons Users List
> Betreff: RE: Technical Support Expiration Date
>
> 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 support for each
> software and make decisions whether to keep the version or migrate to new
> one, depending on longevity of the support given.
>
> I understand that older version will have very limited support for your
> part, hence we should think about migrating to newer versions if we want
> support.
>
> Thanks again for that.
> Regards,
> Sergi
>
> -----Original Message-----
> From: Gary Gregory <[hidden email]>
> Sent: martes, 12 de noviembre de 2019 16:35
> To: Commons Users List <[hidden email]>
> Subject: Re: Technical Support Expiration Date
>
> 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 <
> [hidden email]> 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.
> >
>
> ________________________________
>
> 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.
>