From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: v1.7
Date: Tue, 23 May 2017 11:50:00 -0000 [thread overview]
Message-ID: <20170523114439.GB18266@dinwoodie.org> (raw)
In-Reply-To: <64F4610BDC915A4681532CCAE7ACFDB9344A592A@NAWEPRLHXM01V.nadsuswe.nads.navy.mil>
On Tue, May 23, 2017 at 12:28:53AM +0000, Yamamoto, Anne B CIV PMRF N63 wrote:
> We are currently using v1.7 but it is no longer DADMS supported.
>
> Would it be possible to get a vendor support statement email so that we may continue using this version?
Cygwin is open source software released under the LGPLv3. Now that Red
Hat have stopped providing new Cygwin support contracts, I'm not aware
of anyone who counts as a "vendor" and who would sign up to provide any
particular contractual support for Cygwin.
Furthermore, Cygwin v1.7 stopped being current some time in 2015, and I
don't think even the voluntary support on these mailing lists would be
likely to give you much help with such an old version.
I'm not familiar with DADMS requirements for vendor support statements,
but a very quick search implies they may only apply to commercial
off-the-shelf software. Depending on the precise definitions you're
using, I would expect Cygwin to not count as commercial, which may allow
you to continue to use Cygwin without a vendor support statement.
If that's not the case (and assuming none of the project maintainers
step up to say they're willing to provide such a vendor support
statement), I suspect Cygwin will not meet the requirements for you to
be able to continue using it.
Adam
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-05-23 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 7:27 v1.7 Yamamoto, Anne B CIV PMRF N63
2017-05-23 11:50 ` Adam Dinwoodie [this message]
2017-05-23 22:30 ` v1.7 Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170523114439.GB18266@dinwoodie.org \
--to=adam@dinwoodie.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).