Re: Questions about validation/verification done for Git Software
- From
Stefan Beller <sbeller@google.com>
- Date
- May 8, 2017, 17:21 UTC
- Message-ID
- <CAGZ79kaLMHWth_t7LBpvtAKJQvseS34+RCKoedeqFosUxOiaPg@mail.gmail.com>
- In-Reply-To
- <504208edac024b2dba0c1743dc86683e@AMUSATLWP20005.alereinc.com>
On Mon, May 8, 2017 at 10:14 AM, Robertson, Todd <Todd.Robertson@alere.com> wrote:
Show 13 quoted lines
> Hello, > > I'm a Sr. Software Quality Assurance Engineer at Epocal Inc. in Ottawa, Ontario, > Canada. We are a medical device manufacturer that is required to comply with > the Food & Drug Administration's (FDA) regulations. > I'm in charge of what is known as Non-Product Software, essentially any piece of > SW that is used in the day-to-day work of creating our products. > Part of complying with the FDA regulations is to ensure that all Non-Product Software > has been validated. > > Some of our engineers are planning on using your software "Git" for their software > development processes (latest version) to replace our current software "SVN" and I was > hoping you could answer some questions for me?
How is svn validated for you?
> Are you able to provide me with a copy of your Test Plans and/or Test Cases for the "Git" product?
Tests are found inside the t/ directory in your copy of Git[1]. [1] obtained e.g. via "git clone https://github.com/git/git"
Note that these are just tests; nothing formal attached.
> Is the software FDA certified?
I am not aware of that.
Checkout https://git-scm.com/ and for legal questions contact https://sfconservancy.org/ (via https://git-scm.com/sfc)