From: Per Bothner <per@bothner.com>
To: kawa@sourceware.org
Subject: should we move the Kawa's bug-tracker to gitlab?
Date: Sun, 27 Nov 2016 06:34:00 -0000 [thread overview]
Message-ID: <801889c2-cd68-114d-a280-570c4e105469@bothner.com> (raw)
I think the answer is 'yes" - it doesn't really make sense to use
gitlab for git hosting unless we also use it for bugs/issues.
If for no other reason than people will do so regardless ...
(Though I have mixed feelings about the "pull/merge request" way of working
- and we will always accept old-fashioned patches, we should also
accept merge requests on gitlab which suggests also using their issue tracker.)
For now let's call it an experiment: feel free to report bugs and
issues at: https://gitlab.com/kashell/Kawa/issues
Likewise feel free to host merge requests (pull requests) there.
If the experience is satisfactory I will update the manual
with the above link as where people should report and browse bugs.
I have no plans to migrate the old bugs from Savannah - I don't
know any practical way to do that.
There is nothing very wrong with Savannah's bug tracker,
and in some ways it is more elegantly minimalist and efficient.
However, I think most people would prefer gitlab's.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
reply other threads:[~2016-11-27 6:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=801889c2-cd68-114d-a280-570c4e105469@bothner.com \
--to=per@bothner.com \
--cc=kawa@sourceware.org \
/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).