public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: William Blunn <bill+cygwin@blunn.org>
To: cygwin@cygwin.com
Subject: Cygwin bug tracking is non-existent
Date: Mon, 28 Jun 2010 09:35:00 -0000	[thread overview]
Message-ID: <4C286CD7.6040707@blunn.org> (raw)

Cygwin does not appear to have a bug tracker.

That being the case:

How do we keep all information about a bug together in one referenceable place?

How do we keep a bug around and tracked through to completion?

i.e. How do we do the things that every other project uses a bug tracker for?

Seems like every open source project has a bug tracker.

The various open source foundries seem to provide that as standard.

But no bug tracker for Cygwin.

Consider this a bug report against the Cygwin project.

I'd report it as a bug on the bug tracker, but we appear to have a catch-22 / bootstrapping problem...

Bill


--
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

             reply	other threads:[~2010-06-28  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28  9:35 William Blunn [this message]
2010-06-28 13:40 ` Reini Urban
2015-11-12 10:40 Thomas Schweikle

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=4C286CD7.6040707@blunn.org \
    --to=bill+cygwin@blunn.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).