From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Mark T. Ortell" <mtortell@ra.rockwell.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: List of Known Issues for a particular release
Date: Thu, 11 Jul 2019 16:09:48 +0000 [thread overview]
Message-ID: <20190711160948.GK9224@genre.crustytoothpaste.net> (raw)
In-Reply-To: <CY4PR2201MB1559C26C1D75B4F649AD38049AF30@CY4PR2201MB1559.namprd22.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2436 bytes --]
On 2019-07-11 at 15:28:27, Mark T. Ortell wrote:
> Hello,
>
> I am doing a software tool assessment for functional safety and I am reviewing the use of Git as the SCM. One thing that I need to do is review the list of "known issues" with the Git release being used. I have gone through the release notes and found that it only contains the fixes and enhancements in a particular release of Git, it does not contain a list of known issues/errata in a particular release. The github project also does not include the bug tracking list, so I am not able to figure out a way to review the known issues for a particular release. I considered reviewing the fixes in releases beyond the release used, but that has 2 problems. One, it doesn't contain any issues that are yet to be fixed. Two, only the fixes in the "next" release are truly relevant because fixes after that could have been introduced in a release after the release being used. An additional note is that the Git for Windows project does provide a list of known issues in the install
>
> Could someone in this mailing list assist me in finding the known issues for a particular version?
It sounds like what you're asking is for a bug tracker that lists all
known issues. Git doesn't have one of those; we instead use the mailing
list for reporting issues. We've considered using a bug tracker in the
past, but the idea hasn't caught on yet.
The GitHub project is a mirror; it isn't the canonical resource, and the
Git project doesn't use it for issues or pull requests. Both of these
are also the same policy as for the Linux kernel[0], which you may or
may not use.
If you're looking for an easy way to check off a compliance box, you may
need to work with your management and/or auditors to see what approach
you use for other software (such as Linux) that has nontraditional bug
reporting practices. If you typically use a Linux distro that addresses
this issue for you, then you'll probably want to use Git from that
source as well.
Alternatively, you can use Git for Windows on a non-Windows system; it
should compile and run just fine on Linux, macOS, and Windows, although
it tends to carry more patches than Git itself.
[0] Yes, kernel.org has a bug tracker, but it is known to be incomplete
and many issues are raised only on the various mailing lists.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 868 bytes --]
next prev parent reply other threads:[~2019-07-11 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 15:28 List of Known Issues for a particular release Mark T. Ortell
2019-07-11 15:59 ` Elijah Newren
2019-07-11 19:02 ` EXTERNAL: " Mark T. Ortell
2019-07-11 20:04 ` Elijah Newren
2019-07-11 16:09 ` brian m. carlson [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-12 20:44 Mark T. Ortell
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190711160948.GK9224@genre.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=mtortell@ra.rockwell.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).